Does anyone successfully installed Magisk on their secondary roms using Dualboot Patcher? I tried lots of times, it seems that Magisk 14.0 is installed, but I can't flash in modules like universal safetynet fix, which it always shows that Magisk isn't installed. Also, I cannot pass safetynet, nor can I use Magiskhide. Anyone has a solution? I'm welcome to suggestions. Thanks.
Related
I can't get it to pass the Safety Net test. I've tried all I can think of. Magical has SU hide enabled, Auto magisk is installed, EX has the kernel patch to supposedly get around SN....
Picture of my safetynet helper running attached. I don't know what this issue is... Any idea?
After ROM flash:
SuperSU 2.78 SR1
Suhide
Magisk v8 (I install Magisk because I use systemless Xposed by topjohnwu)
EX Kernel
Rootswitch APK to switch off root
Once you switch off root. SafetyNet will pass.
So I wont say I tried everything but have been reading and trying solutions and they havent worked for me. Maybe someone can point me in a different right direction. So far I clean installed 3.2.8(twice btw), I'm fastbooting into twrp 3.0.2-1, flashed supersu 2.78 SR4 and flashed xposed framework v87.
Sometimes xposed framework v87 flashes in twrp and when I open xposed installer it says xposed framework is not installed. I attempt to then unintstall and try again and sometimes it fails in twrp with this message "cp: cant create '/system/xposed.prop':Read-only file system". I attached a screenshot. I'm also running xposed installer 3.1.1, also tried 3.0.1 by dvdandroid. Any suggestions?
Have you tried Magisk and Systemless Xposed?
mznk said:
Have you tried Magisk and Systemless Xposed?
Click to expand...
Click to collapse
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
SysAdmNj said:
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
Click to expand...
Click to collapse
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
Thanks it all worked and went green except when I tried to download the systeless arm64 sdk23 from within magisk manager. I ended using a test1 version and it went through. Now I wasnt even planning on using magisk but how are you using magisk? When I used it before it was for android pay but I thought that all broke.
Installing xposed breaks SafetyNet anyways and I have no use of Android pay or Pokemon Go etc.
But, with magisk I can install and mod system files without making changes in the system partition like dpi, Viper, SystemUI mods etc. I really like it for the ease of that.
I have installed Xposed on 3.2.8 with a success from the beginning. Steps I've taken:
1. Dirty flashing full zip OOS 3.2.8.
2. Flashing systemless SuperSU from Chainfire (you have to:
Code:
echo SYSTEMLESS=true >> /data/.supersu
for systemless).
3. Flashing Xposed v87-test version, which now disappeared from dl-xda.xposed.info/framework/sdk23/arm64/
4. Flashing ElementalX 0.28.
I was upgrading from 3.2.6.
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
OxygenOS 3.2.7 with v87.1 Magisk version installed. Got stuck at boot animation when dirty flashing to oos 3.2.8. Any ideas? Is there compatibility problem with xposed modules?
I would use a newer recovery, twrp-3.0.2-23-oneplus3 is the latest and I've had zero issues with it. I uploaded it to drive vs searching for it. Next, as stated, install Xposed via the app, version 3.0.1 by dvdandroid is what I'm using and after selecting arm64 api23 , granting root, it installs, reboot and done.
I'm on the global rom. Twrp works fine but the moment I install magisk v19.3 or v19.2 my phone bootloops to twrp
Any ideas? I can run magisk uninstaller and it resolves the bootloop.
Have you tried flashing no-verity-force-encrypt zip? It sometimes helps. I often flash it, just to be save. I have no clue what it does but sometimes it helps haha
It's caused by some Magisk module. I had the same problem when I installed ViperFX. Uninstall Magisk, install it again and then try to install modules one by one to find which one is causing the bootloops.
Don't just install uninstall. It only getting you to twrp after installing magisk. Try magisk manager recovery, you can google it and remove all modules you have after installing magisk. You can reboot and install your module again afterwards.
I havent installed any modules. It's a clean install of magisk. I get a popup asking "requires additional Setup".
If I let that run, it reboots after the Setup. And I'm left with it bootlooping.
Again, no modules installed.
How do you install Magisk to get this popup? Is it the direct install from Magisk manager?
I always install the zip in TWRP. Maybe that will solve your problem if you didn't try this method already.
The other fix could be the zip file mentioned by shisaya24. I used to install it on my previous phone to fix bootloops.
maciek90 said:
How do you install Magisk to get this popup? Is it the direct install from Magisk manager?
I always install the zip in TWRP. Maybe that will solve your problem if you didn't try this method already.
The other fix could be the zip file mentioned by shisaya24. I used to install it on my previous phone to fix bootloops.
Click to expand...
Click to collapse
I install via twrp.
Please help me
Download Xposed installer from https://repo.xposed.info/module/de.robv.android.xposed.installer
Open it, approve for the permissions required and if it is available some zips will show up, else it will tell that it is incompatible
not supported , is there another way ?
Nope!
Except if you downgrade to android oreo, dont do it its not worth it
Also, if you want Xposed for Rootcloak and use magisk i have another solution.
Enable MagiskHide, install MagiskHide Props Config module and enjoy being rooted
what about edxposed, it can be installed from the magisk modules and should be the same. unless op doesn't want magisk installed at all!
I tried to install it but its failed riru-core required , and after i installed it too using magisk i got bootloop issue
I own a firetv stick 2nd gen (tank). I have unlocked the device and installed the Prerooted rom which requires you to install magisk after you install the rom
I just cant figure out which magisk version to use. I have tested 25.2, 25.1, 24.3 but in all these versions the manager just crashing once i press any button on my remote (It doesnt open, it only shows the logo)
I tested 20.03 which luckily works and i had not got time to test any other versions, but i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Lenicyl said:
i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Click to expand...
Click to collapse
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Finnzz said:
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Click to expand...
Click to collapse
hey! For all the versions i installed (which is from the original magisk repo itself), i used the same apk to install both the manager and Magisk itself, so i dont think its signature
mismatch.
I was not aware of any custom magisk builds for firetv until i read your reply. I found this but this has the same issue as normal magisk, the issue being the Manager not working.
Also i just tested Magisk v22 and it works !!
Im thinking ill just stay on this version and i think ill be fine for now ?