I tested most Nougat custom roms. (except Oxygen 4.0.x)
However, none of them worked with Magisk + Phh Superuser. (can't get root access)
(data,cache filesystem : F2FS)
anyone else?
please help...
--
It worked on Sultan's CM13. (MM)
smk513 said:
I tested most Nougat custom roms. (except Oxygen 4.0.x)
However, none of them worked with Magisk + Phh Superuser. (can't get root access)
(data,cache filesystem : F2FS)
please help...
--
It worked on Sultan's CM13. (MM)
Click to expand...
Click to collapse
Magisk v9 + Phh was working fine a month ago when I was using CM14.1.
Don't know which custom roms you were using but many of them have root already included, so you'll have to remove the SU that's included in the ROM before you Magisk + Phh.
Order I've done it in the past:
1. Flash ROM
2. Flash GAPPS (if necessary)
3. Flash unSU Script link
4. Flash Magisk and Phh
5. Wipe Cache/Dalvik (just a habit and a damn good one)
and hopefully you know the rest of the steps.
Magisk v9 works fine with oxygen 3.2.8 (blue spark kernel and data and cache f2fs), but WiFi stops working if I flash v10.2.
Does someone know why? Thanks in advance
My config is a 4.0.1 OOS + 10.2 magisk + phh by topjohnwu v2. Working good so I dunno why you have some issues when we have same phones :/
Mine works with Open 10 beta and did you install the phh superuser app?
Hw4ng3r said:
Magisk v9 + Phh was working fine a month ago when I was using CM14.1.
Don't know which custom roms you were using but many of them have root already included, so you'll have to remove the SU that's included in the ROM before you Magisk + Phh.
Order I've done it in the past:
1. Flash ROM
2. Flash GAPPS (if necessary)
3. Flash unSU Script link
4. Flash Magisk and Phh
5. Wipe Cache/Dalvik (just a habit and a damn good one)
and hopefully you know the rest of the steps.
Click to expand...
Click to collapse
I tested it su removed, so I tried without remove su, but doesn't work.
(Magisk v10.2 + phh v2)
mucha.k1994 said:
My config is a 4.0.1 OOS + 10.2 magisk + phh by topjohnwu v2. Working good so I dunno why you have some issues when we have same phones :/
Click to expand...
Click to collapse
This problem occurs with custom ROMs. other than Oxygen 4.0.x.
adz3d said:
Mine works with Open 10 beta and did you install the phh superuser app?
Click to expand...
Click to collapse
Yes, installed the phh superuser app. I've been using phh since MM.
I read in another thread that on F2FS only the normal phh SuperUser works. I haven't tried it myself though. SuperSU has occasional issues on F2FS as well, irrespective of the ROM (OOS or Lineage based).
I have Magisk and Magisk's phh's superuser on 4.0.1 on F2FS (data partition). Using eng.stk's v11 TWRP, I:
1. Flashed OOS 4.0.1
2. Booted to system, installed some apps
3. Flashed Magisk 10.2, then topjohnwu's r2 phh superuser
4. Boot to system
All works fine.
ememeh said:
I have Magisk and Magisk's phh's superuser on 4.0.1 on F2FS (data partition). Using eng.stk's v11 TWRP, I:
1. Flashed OOS 4.0.1
2. Booted to system, installed some apps
3. Flashed Magisk 10.2, then topjohnwu's r2 phh superuser
4. Boot to system
All works fine.
Click to expand...
Click to collapse
This problem occurs with custom ROMs. other than Oxygen 4.0.x.
smk513 said:
This problem occurs with custom ROMs. other than Oxygen 4.0.x.
Click to expand...
Click to collapse
Okay. In the main Magisk thread someone recently mentioned that phh's r259 was working on DU on OP3. Could give that a bash
ememeh said:
Okay. In the main Magisk thread someone recently mentioned that phh's r259 was working on DU on OP3. Could give that a bash
Click to expand...
Click to collapse
Thanks for the information. i'll try it.
I think it's been well known for a while that phh superuser does not like F2FS. Since like August according to the topjohnwu phh superuser thread.
Related
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.
Actually i want to play Pokemon go on CM. So i'm trying Magisk.
I followed the instruction here and tried with both [Magisk] phh's SuperUser and SuperSU (systemless)
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
But both did not work.
Anybody tried Magisk in OP3 with CM14.1?
Is it possible for magisk to work on CM?
svprm said:
Actually i want to play Pokemon go on CM. So i'm trying Magisk.
I followed the instruction here and tried with both [Magisk] phh's SuperUser and SuperSU (systemless)
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
But both did not work.
Anybody tried Magisk in OP3 with CM14.1?
Is it possible for magisk to work on CM?
Click to expand...
Click to collapse
I was running Magisk V9 with phh Super SU on CM14.1 (late November official nightly) and it was passing safetynet so I know that works, but I never actually tried launching PoGo.
Hw4ng3r said:
I was running Magisk V9 with phh Super SU on CM14.1 (late November official nightly) and it was passing safetynet so I know that works, but I never actually tried launching PoGo.
Click to expand...
Click to collapse
Can you tell me the steps to install?
I think i'm missing something.
svprm said:
Can you tell me the steps to install?
I think i'm missing something.
Click to expand...
Click to collapse
CM14.1 has system root built-in. You have to remove it before you install Magisk and Phh SU. You need unSU http://forum.xda-developers.com/showpost.php?p=63615067.
After you flash the ROM, flash unSU zip. Reboot to recovery again. Flash Magisk and flash Phh SU.
Tikerz said:
CM14.1 has system root built-in. You have to remove it before you install Magisk and Phh SU. You need unSU http://forum.xda-developers.com/showpost.php?p=63615067.
After you flash the ROM, flash unSU zip. Reboot to recovery again. Flash Magisk and flash Phh SU.
Click to expand...
Click to collapse
+1 to @Tikerz response
Tikerz said:
CM14.1 has system root built-in. You have to remove it before you install Magisk and Phh SU. You need unSU http://forum.xda-developers.com/showpost.php?p=63615067.
After you flash the ROM, flash unSU zip. Reboot to recovery again. Flash Magisk and flash Phh SU.
Click to expand...
Click to collapse
Followed the same.
But safetynet check failed. I used https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en.
svprm said:
Followed the same.
But safetynet check failed. I used https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en.
Click to expand...
Click to collapse
There's a few settings you have to enable in Magisk Manager (can't Remeber what they were off the top of my head) and reboot your phone.
You also have to download Phh SU from play store before you can gain access to Magisk Manager
Thanks it worked.
Created a Guide:
http://forum.xda-developers.com/oneplus-3/how-to/guide-play-pokemon-cm-14-1-rom-t3521593
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
phen0m2016 said:
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
Click to expand...
Click to collapse
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
computerslayer said:
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
Click to expand...
Click to collapse
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
phen0m2016 said:
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
Click to expand...
Click to collapse
Honestly, I'm not sure. I don't know if it is possible to upgrade between Android versions via OTA with TWRP installed - I vaguely remember some limitations on OTAs and TWRP. Best to check the official TWRP thread and the readme thread to be sure.
Similarly, I'm not sure about a clean install of Magisk. I've only been using it for about a month so I'm not confident in offering advice about uninstalling - especially since giving bad advice could end up with you not passing SafetyNet because I missed some basic step. I recommend checking out the Magisk forums.
I'm sorry I can't be of more help.
Hello xda community.
I got some knowledge about flashing stuff on my oneplus 3. But Since I use Android oreo beta 29, 30, or stable 5.0 OOS version even when I use the aroma installer from Freedom OS. Magisk doesn't install propobly. .
Im using latest Twrp from Bluespark 3.2.1 -X
I can flash most off the magisk versions 15.0 - 15.1 - 14.6 without bootloops. I tried alot off them but when I boot the phone magisk is not installed.(there is no Magisk app)
When I install the magisk apk. the magisk is also telling me magisk is not installed.
On beta 29 SuperSU was working didn't try it yet on beta 30 but I really want to use Magisk.
I'm reading the forums here also on the OP community but seems like I'm the only one with this problem.
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
theduke7 said:
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
Click to expand...
Click to collapse
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Ghost123NL said:
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Click to expand...
Click to collapse
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
theduke7 said:
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
Click to expand...
Click to collapse
Also not working.
same steps with supersu is working only
Ghost123NL said:
Also not working.
same steps with supersu is working only
Click to expand...
Click to collapse
maybe the only way to make sure is to wipe everything , did you try with custom kernel?
try to flash rom reboot to recovery, then derp kernel (tested and works on latest beta) , then flash magisk... that worked for me at 1st try.
Flash magisk 14.0 and boot see magical working and then update magisk15.3 via magisk manager application.
Use OOS debloater from the themes and apps section to remove some apps from the system. Then reinstall magisk. Problem solved. We have a lot less space left in the system partition and that's the reason magisk is silently failing to install.
Facing same issue
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Shakti Panda said:
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Click to expand...
Click to collapse
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Growtopia Jaw said:
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Click to expand...
Click to collapse
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Shakti Panda said:
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Click to expand...
Click to collapse
Sure, no problem