To summarize all I added to the normal stock d850 instruction for magisk is the setting to uninstall the su binary in super su which takes away root from the rom (directories I beleive), then the full unroot and not flashing the manager instead installing the apk version.
**I did this on the normal official ressurection remix mm for d850**
Walkthrough
**Make sure to make a backup and of course I'm not responsible for bricked devices if you follow this guide with the normal stock d850 magisk install you should be golden besides known bug on bottom**
First use the setting to uninstall su (the binary) then the full unroot
I flashed this bump after flashing magisk and phh superuser 17
http://www.mediafire.com/file/ddq9j99pdy984pc/MR_Bump.zip
**Remember to not update the su binary**
When done flashing magisk, phh superuser 17 and bump **DO NOT flash the manager** (you will trip safeboot). Reboot get phh superuser, say no to updating the su binary, Then you have to find the apk version of magisk manager install that!
Then your good to go
Please note I have not tried other custom ROMs with su built in not sure if all have uninstall su in supersu but if that's the case you have to manually delete the su directories. Other than that they should all work.
**[BuG] The APN doesn't have data connection when the phone starts or is in sleep for awhile. Easy fix is toggleing the airplane mode APN data works within a second**
Sorry for the grammer and whatnot just trying to deliver information
Just in case
This is my original post on reddit.
Custom rom RR mm Magisk walkthrough completed! Pokemon go working!!
https://www.reddit.com/r/LGG3/comments/54v5yl/custom_rom_rr_mm_magisk_walkthrough_completed/
Related
I've updated with the OTA from H14 to H15. I restored the stock recovery beforehand and the update went without Problems.
Before starting the update I tried to "unroot" which also was stated neccessary by SuperSU in two dialogs. But this failed and might be the origin of the problem.
Afterwards SuperSU could not find the su binary so I tried to flash it via TWRP 3.0.2.0 which failed after the line "creating ramdisk backup".
Next I tried to dirty flash the H15 Rom, which also went without problems, but the SuperSU install failed at the same point.
I've attached the logfile of the aroma installer, containing the superSU logfile.
The phone works for the moment, without root / superSU but I would like to have it back
Does anyone have an idea / need more informations / can otherwise help ?
Henry
Anyone know a solution to use banking apps on Rooted Android N since Xposed is not yet available?
The solution is called Magisk ?
After installing, you have at first to enable Magisk Hide, then add the banking apps to the hide list.
Magisk would also be useful for many reasons: survives to OTA (because the system partition is untouched), supports modules like in Xposed (and Xposed too for Android 5.0-6.0), provides a built-in root manager (if you're not a SuperSU user)...
I love Magisk.
To add to the above post, you can't use Magisk for root unless you completely remove SuperSU as your rooting method. You can achieve this by either flashing a cleaner zip or dirty flashing your rom, followed by flashing Magisk.
I have op3 using oos4.0.3 with super su and magisk flashed and checked can u pls guide me through the rest
---------- Post added at 05:09 AM ---------- Previous post was at 05:08 AM ----------
I had supersu before magisk don't know what to do next
BHUSHAN7988 said:
I have op3 using oos4.0.3 with super su and magisk flashed and checked can u pls guide me through the rest
---------- Post added at 05:09 AM ---------- Previous post was at 05:08 AM ----------
I had supersu before magisk don't know what to do next
Click to expand...
Click to collapse
The easiest way to ensure that you have removed SuperSU is to dirty flash your current ROM, then immediately flash Magisk without exiting TWRP. Your phone will remain rooted next time you boot up, though you'll have to re-grant root permissions to each of your root-enabled apps.
Here's what you need to flash in the following order:
1) Stock OOS 4.0.3
2) Magisk 11.1
Simply boot into TWRP, flash 1, wipe cache/dalvik, flash 2, then reboot.
Anova's Origin said:
The easiest way to ensure that you have removed SuperSU is to dirty flash your current ROM, then immediately flash Magisk without exiting TWRP. Your phone will remain rooted next time you boot up, though you'll have to re-grant root permissions to each of your root-enabled apps.
Here's what you need to flash in the following order:
1) Stock OOS 4.0.3
2) Magisk 11.1
Simply boot into TWRP, flash 1, wipe cache/dalvik, flash 2, then reboot.
Click to expand...
Click to collapse
I have SuperSU 2.79sr3 I would like to have it as my root manager
If u flash oos4.0.3 then flash magisk 11.1 then SuperSu 2.79sr3 with edited version which forces systemless mode
Will it work
BHUSHAN7988 said:
I have SuperSU 2.79sr3 I would like to have it as my root manager
If u flash oos4.0.3 then flash magisk 11.1 then SuperSu 2.79sr3 with edited version which forces systemless mode
Will it work
Click to expand...
Click to collapse
I haven't tried flashing SuperSU after Magisk, but I'm pretty sure they aren't compatible.
It will not. Use Magisk or SuperSU, not both.
What about pre-rooted roms?
How can we remove SuperSU and install Magisk?
Flash this unSu script (http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893) and Magisk afterwards.
I tried to install magisk v12 zip but it always fails but says to install supersu soon after. I did that but when i installed magisk manager it said there's no MagiskSU installed and Safety net did not pass as well! Then i tried to uninstall supersu and magisk and flash magisk v12 again but same result again. I tried find how to install MagiskSU online but i can't find any thread about this issue. My aim of installing Magisk is to use MagiskHide for snapchat. Can someone help me pls.:crying:
Are you on SuperSU at the moment?
You will need to unroot using the SuperSU app (That's what I did) before flashing magisk zip.
Secondly, I had trouble with SuperSU + Magisk so I used phh superuser to get it working. I also needed magisk to hide root from snapchat and another banking app and I am able to do so easily.
So, in short,
1. Uninstall SuperSU
2. Flash magisk zip in recovery
3. Flash phh superuser in recovery (People say its optional but I do it anyway)
4. Reboot and benefit
Can you send me a link to download the phh superuser file you used please. When you say uninstall do you mean full unroot? What did you use to uninstall supersu? https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Magisk v12 will auto install root when no root is detected, so u can just clean flash ur rom and install magisk v12 after it, it will auto root
@mharis05 nowadays Phh's Superuser is not "optional": it's unsupported and replaced by the integrated MagiskSU since Magisk v10: look at the official thread, it's declared obsolete.
It would get device in trouble, even if MagiskSU is disabled.
@Bradl79 neither the clean flash is a right way, because:
1) If you're intending a system wipe, it's not resolutive because Magisk is OTA-survival.
2) If you're intending a data wipe, it's an useless waste of time... and data!
You have to run the following zip files: Magisk official uninstaller and UnSU to be sure you've not rooted device in any way.
Then to stay quiet, do a Cache and Dalvik/ART wipe.
At this point, try to reflash Magisk.
I tried that but time and time again when i try to uninstall that SUPERSU it says to flash default boot.img to complete the process. AND Installation "FAILED" Flash Supersu immediately. I did that but still no magiskSU.
At this point try to wipe system and cache/ART, then reflash OOS.
After doing that, go with Magisk.
I am running Android 7.0.0 on my P2 rooted with phh Superuser.
However, I want to switch to SuperSU, which as per my understanding (which is very limited in this matter) will happen after I properly uninstall Superuser.
I have researched quite a bit and found out that phh Superuser does not have an inbuilt unroot option unlike SuperSU.
I also flashed the SuperSU .zip file hoping it would delete the current Superuser, but in vain.
I tried to delete su and busybox from /bin and /xbin using Root Explorer but could not find those files in that location.
So I am really helpless now so as what to do in order to have SuperSU installed on my phone.
Try this:
UnSU Script
Flash in Custom Recovery
Videophile said:
Try this:
UnSU Script
Flash in Custom Recovery
Click to expand...
Click to collapse
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
aeonwiz said:
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
Click to expand...
Click to collapse
Correct, this will only help with removing Root successfully.
You'll then need to root via SuperSu or Magisk or phhSuperuser.
I've made a post about Magisk rooting here that you can follow, this will use Magisk Manager as your Superuser manager.
In that post I mention flashing your original boot.img which will remove any instances of SU you have previously installed if the zip I provided in my previous post does not work for you.
Thanks, I will try that.
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