So I am using EDS app from sovworks.com and this somehow need change SELinux compenents.
It always worked fine untill I have installed Magisk Manager and flashed Magisk v12.
Now Magisk I dont need anymore because Magisk Hide will not work for me. But NOW I CANT USE EDS anymore.
IMAGE:
http://www0.xup.in/exec/ximg.php?fid=14152392
So this notification is normal for me I press OK and it does a fast reboot but now it reboots and it stucks on loading, like a bootloop. And I think this is because Magisk because thats the only different thing I did. It also can be SUHIDE but I dont know.
So i open magisk manager and press uninstall but after the reboot Magisk Manager says Magisk is still installed, its like a damn Trojan and cant get rid of it.
AND NO I AM NOT USING MAGISKSU, i am using SuperSU.
My phone is encrypted too so flashing through TWRP wont work for me.
So headache, you want to use magisk hide it doesnt work and than it DUCKS another important thing with it.
Related
Just installed Magisk on ANE-LX1 by flashing patched_ramdisk and i cannot login in snapchat i tried MAGISK HIDE but didn't work i had to flashed original_ramdisk to login snapchat is there any other way i can use to login?
not sure, but im rooted and use snapchat without magisk hide. ?? have you tired flashing magisk normally instead of patching the ramdisk, thats the way i did it, but when i patched the ramdisk manually i had nothing but problems, try flashing from recovery,
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
jaspad1710 said:
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
Click to expand...
Click to collapse
I'm using V4A as well as the youtube vanced modules, none of them caused any bootloops, the only bootloop i did get was probably only when i used the xposed module.
Here's what you should try, Install magisk manager for recovery mode module and delete every other module, then check them one by one, if they cause bootloops. Install a module, reboot, don't install another one. If you do get a bootloop at any instance, go to recovery mode and open up the terminal in advanced and type in : /data/media/mm then just follow on screen instructions and disable the module causing the bootloop.
franz said:
I'm using V4A as well as the youtube vanced modules, none of them caused any bootloops, the only bootloop i did get was probably only when i used the xposed module.
Here's what you should try, Install magisk manager for recovery mode module and delete every other module, then check them one by one, if they cause bootloops. Install a module, reboot, don't install another one. If you do get a bootloop at any instance, go to recovery mode and open up the terminal in advanced and type in : /data/media/mm then just follow on screen instructions and disable the module causing the bootloop.
Click to expand...
Click to collapse
I guess it was due to multiple mods i flashed in one go. Im with v4a and yt vanced now for almost two days no prob now..
jaspad1710 said:
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
Click to expand...
Click to collapse
I have also installed Magisk and Arise Magnum Opus and now i am in bootloop.
I tried to restore my previous backup, but it was not success.
The phone directly boots into FASTBOOT if i flash LOS16 fresh image and if i flash Magisk along with LOS16, it doesn't show any FASTBOOT but stays in bootloop.
The vendor partition have some weird amount of memory looks like 17592186043943MB!
Please help to recover the issue asap.
I installed YouTube vanced from magisk manager and rebooted directly into recovery and then flashed the notification icon enabler from TWRP and was then just bootlooping to TWRP. I uninstalled the notification enabler with the disabler given by the same website but the phone still bootlooped. I uninstalled YouTube vanced from TWRP terminal but the phone still bootlooped. Tried to restore a nandroid backup but in vain.
The only thing that seemed to be working was uninstalling magisk using the official uninstaller and the phone booted to system but I obviously lost root.
Had to flash the ROM through fastboot which formats the phone and then unlock , install TWRP and root again.
Waking up with a sleepy head I wanted to swipe the new version notification away, but didnt swipe well enough and it actually upgraded. I need to downgrade to v23 again but for whatever reason, its not working. Here's what I tried:
1. Reboot to fastboot and do fastboot boot magisk_patched.img (boot img with magisk 23 I use after OTA's). This boots but its not rooted. Magisk mgr is 24 though.
2. Rebooted to system, uninstalled Installed magisk manager 24, rebooted and retried the above. Installed Magisk mgr 23. No root.
I then unpacked the latest full oos 11 for my phone with payload_dumper, copied the boot.img to my phone and patched it using magisk manager 23. Copied it back to the PC.
retried step 1. No root.
Rebooted to fastboot again, checked current slot, its A.
fastboot flash boot magisk_patched.img (the new one I patched in the step above).
Rebooted, no root.
What am I supposed to do to get Magisk 23 back on my phone?
The reason is I'm dependent on riru/lsposed for a couple of xposed modules. If I disable zygisk in magisk 24 I won't have root hide, if I enable that, riru/lsposed isn't working.
Thanks for the help!
Yeah I had a similar issue on A12 rom, Magisk 24 just doesn't allow me to pass safety net due to Google play services in Magisk 24 deny list unselects after a reboot, so downgrading to 23 which just works after using hide list.
I had to disable and remove any modules, unhide Magisk 24 then restart.
Use Magisk 24 uninstall in the app and restart.
Install Magisk 23 and Install to boot image file to payload Boot.img, restart to Fastboot and flash as you did.
Then again in Magisk install select Direct Install then restart.
Reapply Magiskhide to apps google pay/services etc restart and check root.
I still have an issue with Magisk hiding the app installs the proxy app but it doesn't open so isn't working, so still working on this. Root is working tho with the above.
Thanks, I still cant get it to work though.
I can patch the boot.img, but when I try to boot it I don't get root.
When I flash and boot it, there still is no root available.
Possibly i had the same issue, no root after flashing the 23-modified boot image. I solved it by, upgrading the app to 24.3, patch the boot image, reboot to fastboot, flash it, reboot it so i was back at Magisk 24.3 Then i did a full uninstall of Magisk, via the app. Then installed app v23. Patched the boot image etc as per https://topjohnwu.github.io/Magisk/install.html#patching-images
Key here was, i think the full removal of Magisk 24 before downgrading.
Hi guys, will Twrp be available for this device so I can root it with Supersu, instead of Magisk, couldn’t get Viper4Android and Adaway run properly with Magisk.
Yes, TWRP will be available, I tried making it for now with a dump but failed, waiting the real sources.
Also, use magisk lol, supersu is ancient and doesn't work. It's impossible that magisk didn't worked with those apps
I think it didn’t work cause of systemless root
TroyCas99 said:
I think it didn’t work cause of systemless root
Click to expand...
Click to collapse
Well no idea, all that I know is that Adaway and 99% Viper is working fine with Magisk.