Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
Yes, it works for me and I installed couple of modules as well...
Great thanks will try again.
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
marvi0 said:
Great thanks will try again.
Click to expand...
Click to collapse
gigatex said:
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
Click to expand...
Click to collapse
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
For me I noticed I have to reboot when I install each and every module. On my oneplus-5t I could install a bunch and then reboot once but on the pixel presumably due to the new firmware, you have to reboot after each module is installed and this definitely helped me.
Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
gigatex said:
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
Click to expand...
Click to collapse
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Badger50 said:
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Click to expand...
Click to collapse
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
gigatex said:
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
Click to expand...
Click to collapse
Don't know what to tell you my friend. Grab some install logs and head over to the magisk forums for some additional help is all I can suggest. I wish you luck :good:
I'm trying to figure out where i went wrong, because the last time i tried ROOTing PDP3, i couldnt boot and i am yet to see and PDP3 Patched_Boot.img or TWRP Recovery...
I did the following:
-Fastboot Flash-ALL PDP3
-Boot and set-up device PIN
-Boot into Fastboot
-Fastboot boot TWRP3212.img
-Use TWRP Installer to install Custom Recovery on device
-Reboot Recovery
-Flash Magisk v16.4
-REBOOT SYSTEM
-I think i ended up Looping @ G
Related
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?
humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.
Check out this post, it works like a charm.
This is actually relatively simple, and has worked with every update on Oreo.
Use at your own risk, while it's unlikely something like this will brick your device, I take no responsibility if anything happens. Always know how to get yourself out of a bootloop. The APKs and Magisk module posted by others should be fine, however feel free to extract the APK yourself from the Pixel 2/3 factory images.
Download the APK here (or extract it from the Pixel 2/XL's P DP1 factory image), install TWRP and Magisk (I used v16). Use a file manager with root permissions, I used ES file manager. Copy Framework-res__auto_generated.apk from here to System/Vendor/Overlay/ and overwrite (you could also copy the original somewhere if you wanted a backup). SystemUI will crash or the phone will reboot. Due to this, apps will constantly be crashing, to fix this, open up the file manager again and set the permissions correctly.
(Incase anyone is curious why I don't have a navbar, I removed it with a buildprop edit, I'm a bit nervous about burn in, and that way I can avoid it. Also, AOD moves around slowly)
Based on what I've seen with the leaks from the Pixel 3, it may be this simple to get the AOD with a wallpaper when we get the file from the Pixel 3 XL. But then again, I'm not a developer, so maybe not. But I'm glad this is still working for now!
APKs are posted by various users here, once I get access to my PC I'll be sure to post them in chronological order every time a update is put out.
Magisk module here https:/forum.xda-developers.com/pixel/themes/mod-display-enabler-magisk-module-t3857034
But doesn't magisk not work?
muppetmaster916 said:
But doesn't magisk not work?
Click to expand...
Click to collapse
That's what I thought, it seems it's just a Magisk manager issue, root works but not in all apps. Worked fine with a file manager for me.
Doesn't work for me. Everytime I navigate to root folder, it comes up blank
dictionary said:
Doesn't work for me. Everytime I navigate to root folder, it comes up blank
Click to expand...
Click to collapse
Did you install Magisk via TWRP? Only other thing I can think of, is going back to 8.1, rooting and giving the file manager root permissions, then flashing P (as a update, without wiping data) then flashing Magisk again. Then opening the file manager, it will already be able to use root permissions. It seems like it's just the Magisk app that is broken, not root itself.
YTSec said:
Did you install Magisk via TWRP? Only other thing I can think of, is going back to 8.1, rooting and giving the file manager root permissions, then flashing Oreo (as a update, without wiping data) then flashing Magisk again. Then opening the file manager, it will already be able to use root permissions. It seems like it's just the Magisk app that is broken, not root itself.
Click to expand...
Click to collapse
Yeah. It's not so serious to do all that work lol. I'm sure a real solution will come soon, but thank you
What's the battery hit? Negligible?
nadiros said:
What's the battery hit? Negligible?
Click to expand...
Click to collapse
It's just a disclaimer they have, I have been using AOD since early December with no battery issues.
Tried this on Android O March 2018, extracted the file from Pixel 2 XL factory images, but I'm not getting the option in setting.
Do I have to do anything else other than copy file and set permissions?
Edit: Read your other thread, and did it through TWRP file manager as I don't have root. I guess it only works using a file manager with root while booted.
Sent from my Pixel XL using Tapatalk
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
nadiros said:
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
Click to expand...
Click to collapse
The system isn't booting or you are having other issues?
Any way to enable this without root? Like for Oreo installing the Substratum and Andromeda plugin?
nadiros said:
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
Click to expand...
Click to collapse
Yeah I'm up and running. I moved the file, rebooted, got into ES file (after a few tries) and was able to fix the permissions. I'm on Dev preview with magisk and a few modules + this mod now.
muppetmaster916 said:
Yeah I'm up and running. I moved the file, rebooted, got into ES file (after a few tries) and was able to fix the permissions. I'm on Dev preview with magisk and a few modules + this mod now.
Click to expand...
Click to collapse
Great, glad it worked out. I'm having issues with Magisk though, no modules seem to work. Did you do anything different to get them working?
jidccruz said:
Any way to enable this without root? Like for Oreo installing the Substratum and Andromeda plugin?
Click to expand...
Click to collapse
I don't think so, unfortunately. I tried via TWRP and nothing stuck until I rooted.
YTSec said:
I don't think so, unfortunately. I tried via TWRP and nothing stuck until I rooted.
Click to expand...
Click to collapse
Will try your workaround. Hopefully it works. I'm already in Android P? Any way to install TWRP and Magisk without clearing data?
jidccruz said:
Will try your workaround. Hopefully it works. I'm already in Android P? Any way to install TWRP and Magisk without clearing data?
Click to expand...
Click to collapse
As long as you have a unlocked bootloader (which you should if you are on the first P preview, even though it is insanely stable) it won't wipe your device. Magisk was actually updated to work with P.
YTSec said:
As long as you have a unlocked bootloader (which you should if you are on the first P preview, even though it is insanely stable) it won't wipe your device. Magisk was actually updated to work with P.
Click to expand...
Click to collapse
Thanks for the info. Will try it now!
Magisk has just been updated to support Android P
YTSec said:
Great, glad it worked out. I'm having issues with Magisk though, no modules seem to work. Did you do anything different to get them working?
Click to expand...
Click to collapse
Choose download rather than install, within magisk, then use twrp to flash.
Okay here's what happened: I installed Magisk on Android 10 by patching the boot image and flashing from fastboot. This worked great. I installed a few modules, rebooting after each one to ensure it was still functioning. Then I got to a bad one (Riru EdXposed) and it stopped booting fully.
But now I can't disable the bad module to get just Magisk back. I can disable Magisk entirely by going to the old boot image but as soon as I boot a patched image to get Magisk back, the bad module is enabled and it won't boot fully.
Previously I would have used MagiskManager to resolve this from TWRP but TWRP is not released for Android 10 yet.
Any suggestions?
fysix said:
Any suggestions?
Click to expand...
Click to collapse
I believe this is the thread that explains what to do: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867
Exokan said:
I believe this is the thread that explains what to do: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867
Click to expand...
Click to collapse
That looks like exactly what I need! I'll give it a try. Thanks!
i've been trying for 2 whole days now to install viper4android on my oneplus 9 pro, i just can't get it to install. I'm basically stuck in an install loop and i've tried almost everything (permissive, AML, clean install, v4a repackaged, android 12 fix) but none of them work.
I wonder if anyone got viper working on their device running a custom android 12 rom
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Hammerhand.17 said:
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Click to expand...
Click to collapse
tried that too and just now tried it on just stock lineage os on A11 but still no luck nstalling v4a
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Hammerhand.17 said:
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Click to expand...
Click to collapse
i did follow every step with the reboots after each module but i'm still stuck in an install loop so i cant even get to the settings unfortunately... i've never had so much trouble with a device
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
Awesome, i'll try as soon as a custom rom is up and running
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
So install magisk, reboot, AML, reboot, JamesDSP, reboot, V4A, install drivers and let it reboot? kernel can stay in enforcing?
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Hammerhand.17 said:
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Click to expand...
Click to collapse
Got it working finally!! Could you supply me with the modification i need to make in the post fs file? So i follow you exactly? Also can i remive jamesdsp now or does it need to stay installed?
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Hammerhand.17 said:
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Click to expand...
Click to collapse
But can i remive jamesdsp from magisk or does it need to be installed in order to keep viper working? Like the moment you remove it viper just stops working?
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Hammerhand.17 said:
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Click to expand...
Click to collapse
If you uninstall it viper is once again stuck in an install loop so you do need jamesdsp to stay installed
Ok. Good to know. Will left it installed, then.