Hi,
I was recently having some trouble with Magisk in that I flashed it however didn't gain root so I uninstalled it and thought I would try with SuperSU however upon flashing SuperSU then trying to flash Magisk there was an error with Magisk saying that there isn't enough space in the boot partition and to delete some ramdisks and right now I am at a complete loss at what to do. (SuperSU - V2.79 | Magisk - V11.6)
Any help at all is appreciated, thankyou
dasbiz said:
Hi,
I was recently having some trouble with Magisk in that I flashed it however didn't gain root so I uninstalled it and thought I would try with SuperSU however upon flashing SuperSU then trying to flash Magisk there was an error with Magisk saying that there isn't enough space in the boot partition and to delete some ramdisks and right now I am at a complete loss at what to do. (SuperSU - V2.79 | Magisk - V11.6)
Any help at all is appreciated, thankyou
Click to expand...
Click to collapse
Hi,
Try flashing the magisk uninstaller found here, then reflash magisk V11.1 found here
Magisk 11.6 is bugged.
- renolz
renolz said:
Hi,
Try flashing the magisk uninstaller found here, then reflash magisk V11.1 found here
Magisk 11.6 is bugged.
- renolz
Click to expand...
Click to collapse
Thanks! This fixed it and now I have Magisk working however was wondering if you know whether Viper4Android's Magisk Module would work with the S6 or there are more steps to follow if installing to a Samsung device?
dasbiz said:
Thanks! This fixed it and now I have Magisk working however was wondering if you know whether Viper4Android's Magisk Module would work with the S6 or there are more steps to follow if installing to a Samsung device?
Click to expand...
Click to collapse
Hi,
That depends on your kernel and what android version you are on.
Take a look at this guide, read the last pages for a little gudie on how to do it
Official V4A page can be found here, under post #2 you can read where it says "For Samsung devices"
Hope this helps.
- Renolz
Related
Anyone know if I need to downgrade to MM and re-flash twrp to get Magisk working for systemless root?
I can install SuperSU but Magisk automatically reboots the phone while flashing the Zip file in twrp.
Zekisu said:
Anyone know if I need to downgrade to MM and re-flash twrp to get Magisk working for systemless root?
I can install SuperSU but Magisk automatically reboots the phone while flashing the Zip file in twrp.
Click to expand...
Click to collapse
No Magisk possible on N.
Read up on it here: https://forum.xda-developers.com/honor-8/how-to/info-loop-support-7-0-emui-magisk-t3578091
N01tra said:
No Magisk possible on N.
Read up on it here: https://forum.xda-developers.com/honor-8/how-to/info-loop-support-7-0-emui-magisk-t3578091
Click to expand...
Click to collapse
Cool ty for your reply.
Also all versions after 11.1 break the fingerprint sensor.
Magisk kernel is currently being worked on .ETA 10 days , check the post in the Dev section
+
Please help me!!
So I runned the magisk zip in twrp but in magisk maniger it only says that magisk is installed, not that its rooted
If you know something about this or can help me, please react.
Thanks
Yes it dosnt root thats why i downgraded to maarshmallow...with original super SU...magisk is waste of space and time for nougat
Rubster477 said:
Please help me!!
So I runned the magisk zip in twrp but in magisk maniger it only says that magisk is installed, not that its rooted
If you know something about this or can help me, please react.
Thanks
Click to expand...
Click to collapse
Go to the magisk thread and make sure you have the latest magisk v12.0 zip... also download the uninstaller zip.
Once in awhile with samsung devices you'll lose root with magisk. It helps if you boot into twrp and flash the uninstaller zip (might be best to backup first... Beware, if you try to boot phone after running the uninstaller zip, you will more than likely get bootloop...) Then without rebooting the phone, flash magisk v12 zip.
It should work. Its also good to wipe davlik every so often.
Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
bramhc said:
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
Click to expand...
Click to collapse
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
yldlj said:
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
Click to expand...
Click to collapse
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
bramhc said:
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
Click to expand...
Click to collapse
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
yldlj said:
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
Click to expand...
Click to collapse
Okay. Will try now. Thanks
EDIT: Confirmed. Viper4android works. Maybe it's James DSP that hasn't been updated to work with Pie. Cheers.
I was thinking of trying to fix a few minor things like won't boot with charger plugged in and Google Pay getting screwed up every once in a while...but figured I would ask first.
To be safe I was going to nandroid backup, TWRP Magisk Uninstaller, TWRP Magisk 18.1 installer and try it out later on....it seems people have reported bootloops on other phones upgrading from the Magisk Manager app...
MW
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
0xPraeT0Rian said:
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
Click to expand...
Click to collapse
Using the new magisk 18.1 or 18?
You asked about 18.1.
I am on 9.0.3 with 18.1 magisk and the new magisk manager
Hi to all,
I am on OB12, and I'm no longer able to root since I tried to upgrade from Magisk 18 to 18.1
I already tried the 2 last versions of Magisk uninstaller and also to reflash OB12, but still impossible to root.
What is very strange is that if I flash Smurfkernel it says that I'm rooted, but after booting, no Magisk APK and impossible to install it !
Any suggestions?
Thank in advance for any help.
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
No problems here.
b.huss2 said:
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
Click to expand...
Click to collapse
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
OP here -- I updated and am having no issues, but I did it all through TWRP by uninstalling Magisk 18.0 first and then re-installing 18.1 before rebooting. I had already updated Magisk Manager from the app.
Only thing I noticed was I had to reset up all my settings (Magisk hide for Direct TV Now, and re SU authorize all root apps). First reboot everything was slow with root apps waiting for SU access before the request came through, but then everything was fine once it was granted.
michelD said:
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
Click to expand...
Click to collapse
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
b.huss2 said:
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
Click to expand...
Click to collapse
Yes I tried this too, but unsuccessfully !
And I'm even not sure that a full wipe will help, because it concerns another partition.
I managed to root the device...but didn't have much luck with Edxposed yafa Has anyone managed to get Edxposed working on a S10e yet ? If so which variant
Tried both Variations on my SM-970F , YAHFA and Sandhook. Both hung up the phone at the Samsung logo
Edxosed Canary worked
On my S10e with BeyondROM V6.7 it works fine.
I have the following software istalled:
- Magisk 20.4
- Riru-Core v19.8
- Riru-EdXposed v0.4.6.2 (4529) (YAHFA)
- EdXposed Manager v4.5.7 (Enhancement mode)
The modules that I am using: AFWall+, XPrivacyLua
Same exact setup/config: Interested in knowing how you did it?!
gl000008 said:
On my S10e with BeyondROM V6.7 it works fine.
I have the following software istalled:
- Magisk 20.4
- Riru-Core v19.8
- Riru-EdXposed v0.4.6.2 (4529) (YAHFA)
- EdXposed Manager v4.5.7 (Enhancement mode)
The modules that I am using: AFWall+, XPrivacyLua
Click to expand...
Click to collapse
Its good to see evidence that some one with the device I have just purchased is using the same software loadout as I will be. So I have a few questions -
Regarding magisk install, how did you get this installed? or did you follow JohnWu's instructions on his magisk page..?
Also what recovery are you using, is it twrp and if so what version..?
In what sequence did you install magidsk, twrp, xposed..? Which thread/guide on XDA did you use/follow..?
are you able to reboot the phone normally? or if not why not and what are you work arounds?
is one of the fixes for rebooting, powering off/on the phone to flash Multi-disabler?
and lastly have you had any freezing of crashing issues related to Xposed or any Xposed modules..?
As your post is a few months ago and EdXposed, RiRu/, Magisk have been updated since then, what version are you currently running?
b1k3rdude said:
Its good to see evidence that some one with the device I have just purchased is using the same software loadout as I will be. So I have a few questions -
Regarding magisk install, how did you get this installed? or did you follow JohnWu's instructions on his magisk page..?
Click to expand...
Click to collapse
I followed the installation instructions from the BeyondROM thread. I also read many comments in that thread that clarified some doubts, but I don't remember exactly which messages.
b1k3rdude said:
Also what recovery are you using, is it twrp and if so what version..?
Click to expand...
Click to collapse
The BeyondROM requires installation of Ian’s latest patched TWRP. I used version 3.3.1-103. In order to install TWRP I followed the installation instructions in that thread and read many messages to clarify the instructions.
b1k3rdude said:
In what sequence did you install magidsk, twrp, xposed..? Which thread/guide on XDA did you use/follow..?
Click to expand...
Click to collapse
As indicated above, to install the TWRP, BeyondROM and Magisk I used the instructions in Ian's TWRP and BeyondROM threads. Several other messages inside the threads also helped, by I don't remember exactly which ones.
To install EdXposed I used Magisk Manager to download and install the following modules:
Riru-Core v19.8
Riru-EdXposed v0.4.6.2 *4529( *YAHFA)
Then I installed the APK EdXposed Manager v4.5.7 from this page https://github.com/ElderDrivers/EdXposedManager/releases
After restarting the phone, I installed some EdXposed modules from within the application and enabled them, which also required another phone restarting.
b1k3rdude said:
are you able to reboot the phone normally? or if not why not and what are you work arounds?
is one of the fixes for rebooting, powering off/on the phone to flash Multi-disabler?
Click to expand...
Click to collapse
I reboot the phone normally and it restarts in rooted system. This features is provided by BeyondROM and I didn't have to do anything extra.
b1k3rdude said:
and lastly have you had any freezing of crashing issues related to Xposed or any Xposed modules..?
As your post is a few months ago and EdXposed, RiRu/, Magisk have been updated since then, what version are you currently running?
Click to expand...
Click to collapse
I haven't experienced any freezes or crashes in all this time. The only modules that I installed are: AFWall+ and XPrivacyLua.
I haven't updated any software (TWRP, ROM, Magisk, EdXposed) and now there are more up to date packages of all of them.