Whenever I try to install it via Magisk and I reboot, my TWRP just sends me to rescue mode. I've tried experimenting it multiple times but it does the same thing. I've tried doing it with the root method where I use an installer in TWRP, but it doesnt work. Anyone knows how to fix this?
Android being android. I'm facing an issue with Netflix: when hdr content are playing is too dark, barely visible.
Since I have seen other people complaining, I believe is my unique problem. I'm saying that because I haven't seen people complaining about vanced.
Pehaps, you should wipe data. And satr the rom as clean flash. We create those problems by dirty flashing or not flashing stuff right. You could try also deleting all your modules and using magisk 19.3 or 20.0
Install mom root version. It works fine. Non root is more latest version too
Related
Hi all,
My system was working fine with Magisk v12, I saw there was a big new update, I was interested and updated.
But using the latest Magisk Manager, it says root is not detected.
It's not a big problem, I will restore back to v12 for now, but did anyone else get it working?
Thanks
Asus zenfone 2 flash update manual Magisk 13.1 crash recovery recovery then AD
Same here with Xperia XZ. With v13.1 Root is not detected. v12 is working fine.
Have tried to reinstall it by completely removing and flashing from TWRP, but still no luck.
13.1 and 13.2 working on 7.1 with repacked stock kernel with drmfix fix. It will also work with newest genesis kernel
I upgraded Magisk 12 to 13 beta, then 13.1 and 13.2 without problems.
Even SafetyNet Check passes.
I'm using genesis-nodrm kernel.
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
qvmuhuuxz said:
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
Click to expand...
Click to collapse
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
realtuxen said:
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
Click to expand...
Click to collapse
Ok I'll try that.
I believe I flashed v13.2 straight over v12.
But when downgrading back to 12, I did flash the uninstaller first.
I'll try uninstalling and then updating
- Still no luck, it didn't work.
I tried updating Magisk 12 -> 13.1 thru the manager, and it would download the zip then do nothing. I found the zip in the Magisk directory, and installed it like it was a module, thru the manager, and it appeared to work. I got the new Magisk Manager (5.0.4) and it says I'm on Magisk 13.1 but that Magisk is not installed, and there is no root.
Following the installation instructions, I rebooted a few times, no change. So I flashed Magisk uninstaller, cleared cache/davlik, and rebooted. Uninstalled Magsick Manager. Rebooted. Booted to TWRP and flashed Magisk-13.1.zip. Rebooted twice. Same issues; Manager 5.0.4 says I'm on Magisk 13.1 but that it's not installed, no root.
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
voilsb said:
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
Click to expand...
Click to collapse
I didn't have to reboot after flashing magisk uninstaller, I just flashed v12 straight after.
And I just uninstalled the new magisk manager then the old one right away, I think?
Magisk manager 13.1 not working for me either tried installing thru app but it does not work
might be related to this https://github.com/topjohnwu/Magisk/issues/265
Also it might be related to this - https://github.com/topjohnwu/Magisk/issues/166#issuecomment-298765812
"Use rootkernel tool from tobias.waldvogel to fix drm instead of PoC TA fix. It seems to be incompatible to Magisk while rootkernel tool patched images work"
I swapped over to Genesis kernel (1.05, the current latest) to try and see if it would help my device pass safety net, since for some reason it is not passing anymore (I tried lots to fix it, flashing etc)
As I posted directly above, it looks like Magisk v13 doesn't like ta_poc, so I used the drmfix version, and Magisk v13.3 works great, and once again my device passes safety net
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Have you tried to change your twrp? What's the exact file name of it? Did you tried magisk 17.1?
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Phone is starting is a bug on cr droid, los also. I don't know fixes. But don't worry you are not the only one with this issue.
Try Magisk beta 19.0. I had the same problem as you with 18.0 and 18.1, but 19.0 solved it for me...
Hi guys!
First of all, please do not send me to somwhere on forum because I have tried dozen of ways do deal with problem. My phone is LG G6 running on android pie. TWRP installed, Magisk installed. Im trying to instal viper4droid. I have tried download module from Magisk itself, I have tried to download .apk file from different sources, I have tried to download .zip file, I have tried to installed as apk itself and grant root accesss, tried by TWRP, tried unify installers and **** knows what else. Trouble is, First few times it was installed but status was "not running", Today after many attempts to deal with that viper4droid installing drivers and.......after each reboot its doing it again. Moreover i have found that sometimes Magisk did not show up the newest version of v4a as a module to download. So......is somebody for the love of god know what the **** is wrong? thank you.
marcin3595p said:
Hi guys!
First of all, please do not send me to somwhere on forum because I have tried dozen of ways do deal with problem. My phone is LG G6 running on android pie. TWRP installed, Magisk installed. Im trying to instal viper4droid. I have tried download module from Magisk itself, I have tried to download .apk file from different sources, I have tried to download .zip file, I have tried to installed as apk itself and grant root accesss, tried by TWRP, tried unify installers and **** knows what else. Trouble is, First few times it was installed but status was "not running", Today after many attempts to deal with that viper4droid installing drivers and.......after each reboot its doing it again. Moreover i have found that sometimes Magisk did not show up the newest version of v4a as a module to download. So......is somebody for the love of god know what the **** is wrong? thank you.
Click to expand...
Click to collapse
Hi man, there are three versions of viper4ndroid on magisk, try the viper4android fx legacy materialized as normal app after disabling play protect on google playstore. hope this helps
I will try that in a minute mate.
didnt work.
I have the same problem. I switched to viper hifi and now after reboot it is working but after some time it stops till i reboot it again. I think it is because of the pie version, on oreo everything works fine. After every reboot every mofule in magisk reinstalls. For example youtube vanced instals like new and i have to set it up after the reboot.
IIRC it required me to install viperfx (the new version, not legacy or xhifi), audio modification library and audio compatibility patch, have you done that?
I have tried all three version of viper. I have isntalled it as a apk and modules in Magisk. All possible audio patches and compatibilies mods from magisk are intalled as well.
marcin3595p said:
I have tried all three version of viper. I have isntalled it as a apk and modules in Magisk. All possible audio patches and compatibilies mods from magisk are intalled as well.
Click to expand...
Click to collapse
if you still have this problem, try installing viper4android 2.7 as apk from xda lab, I was downgrading back to pie sometimes ago and couldn't get viper to work, besides the 2.7
I am in need of assistance.
I am using a OnePlus 8 Pro (EUR)
After using stock magisk rooted OOS 10 for quite a while I updated to OOS 11 and rooted it again.
All goes well until an hour or 2 have been passed.
After those 2 hours my banking apps won't show anything more than a blank screen. Some apps won't open or start freezing on launch. All with Magisk Hide enabled.
Strangely enough, Magisk manager still says that I'm passing safetynet.
I have tried to root my OP8Pro on OOS 11 several times but I will get these problems eventually. Sometimes combined with a bootloop.
Has anyone else also had this. And if so, is there a way to fix this? I would be glad if I can root my phone again.
Help will be appreciated.
ps: I am aware that this thread has to be moved somewhere else.
I really don't know what's causing the issue you're having but I highly recommend to do a backup and then factory reset, it could fix all the issues
I was having reboot and freeze issues. I had to follow the unbrick method for a full clean slate, have been good since aside from some rogue apps lol
Sounds like you've booted the magisk patched IMG and then not made it permanent by installing directly afterwards.
Apps can begin to fail after turning on systemless in magisk. You are meant to reboot which would inadvertently disable root if you haven't installed directly after booting like I said
If you have 100% installed directly and it survives a reboot then it is more than likely your boot IMG, reobtain another and patch it with the latest magisk beta. Then boot it then install directly.
Reboot to see if it's taken.
Then go systemless and magisk hide.
Then reboot.
dladz said:
Sounds like you've booted the magisk patched IMG and then not made it permanent by installing directly afterwards.
Apps can begin to fail after turning on systemless in magisk. You are meant to reboot which would inadvertently disable root if you haven't installed directly after booting like I said
If you have 100% installed directly and it survives a reboot then it is more than likely your boot IMG, reobtain another and patch it with the latest magisk beta. Then boot it then install directly.
Reboot to see if it's taken.
Then go systemless and magisk hide.
Then reboot.
Click to expand...
Click to collapse
Ok, I will try it out, thanks!
Apexrajang said:
Ok, I will try it out, thanks!
Click to expand...
Click to collapse
Very welcome sir
some of my bank apps only work with private dns, for some reason, otherwise they show random bugs about "slow connection" or whatever