Related
Anyone know why it wont stay
Ssys no batty
Says no binary installed
pbedard said:
Says no binary installed
Click to expand...
Click to collapse
1st, did you flash the SU file? 2nd, what rom are you on?
Yes 5 times 2 im using dev digitals rom im on sprint
pbedard said:
Yes 5 times 2 im using dev digitals rom im on sprint
Click to expand...
Click to collapse
The latest SU File? which is SR3 2.79? if it didnt work try the Unsu.zip file to remove SU and then flash the SU file again. see if that works.
Devdigital help me thanks
pbedard said:
Devdigital help me thanks
Click to expand...
Click to collapse
did you flashed the unsu file then flashed the Su file?
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
pbedard said:
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
Click to expand...
Click to collapse
AAhh i see. Now i know where you are standing at. you are using magisk. But do you have magisksu ? or keep having supersu as main root but magisk installed? . What i mean to say is, when you go into the magisk app, in the 2nd box of the main screen, does it shows supersu as root method? or magisksu? if it is magisksu then you dont need supersu, now, if it does says supersu, then you do have to fix the issue of supersu to unroot by using supersu function and then go directly into recovery mode and flash magisksu once again.
It says majisksu
pbedard said:
It says majisksu
Click to expand...
Click to collapse
then you dont need su (unless you want it). It is because you already have magisksu (which is pretty much doing the same as su). one overrides the other and then one gets thrown out. Usually to install magisk manually, one does as follows:
1) install magisk app from playstore
2) give supersu access (granted to magisk su)
3) use unroot function in supersu
4) flash magisk zip in recovery mode.
Now, there are other methods to achieve magisksu but the point is that maisksu has changed the binary (which is what SuperSU is telling you that you dont have).But that doesnt mean you are not rooted. you are already rooted with magisk and can achieve pretty much anything that you could achieve with supersu. (it will ask you for prompts asking you whether you want to give su access to "x" or "y" app. etc... Now, if you want SuperSU, you could try to flash the magisk uninstaller. Then do the process of rooting that has been specified for your phone. That should return the SU binary to normality . (this assuming you try to unroot and then flash SU back but didnt work)
hey guys bought my ls997 used. has root because i get the flash screen (untrusted)and twrp is installed and working. how do i find out which to flash ? any advantages to use supersu over magisk ?
i installed magisk manager and it states no root found.
Majisk u have to turn root access on majisk works alot better
@pbedard
Did the help @jinkerz9430 gave work for you?
Yws
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system (Edit 8/28/17: DO NOT install TWRP, just boot to system)
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
UPDATE 10/2 The links for SuperSu and SuHide have been updated to the latest releases.
GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
GroovinChip said:
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?
raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
I've seen some folks report that they couldn't get Magisk to work. I can't confirm that right at this moment though. You can test and see if it'll work by just using the TWRP provided. Not sure if it's based off RC2 or RC1.
raazman said:
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?
Click to expand...
Click to collapse
It depends, are you able to boot to system? If not, like you're stuck in a bootloop, I'd suggest flashing completely back to stock. It would mean you'd lose your apps and data, but if you can't boot to system anyway then it doesn't really matter.
If you CAN boot to system, then I'd suggest just starting over and use SuperSu with SuHide. I doubt that any changes actually took place on your device since you didn't flash a custom kernel. But this is only if you can boot to system successfully.
Sent from my Google Pixel XL using XDA Labs
Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.
GroovinChip said:
3) Download SuperSu Config
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
Click to expand...
Click to collapse
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.
Mike02z said:
Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.
Click to expand...
Click to collapse
Great!
I haven't tested my debit card after adding yet either. Been home the whole time
Sent from my Google Pixel XL using XDA Labs
@GroovinChip Is your bootloader unlocked?
Kisakuku said:
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.
Click to expand...
Click to collapse
Ok, I'll edit the OP. I wasn't 100% sure, that's why I did it anyway.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Rooted perfect however I cannot uninstall system apps, how come?
have you tried going into adb shell and type the su command?
I'm using the system app remover from playstore. It says failed to uninstall.
Root works. AndroidPay works with SUHide!
Thanks!
Ok after reflashing, everything works as intended. Thanks for the guide!
I can confirm this works with the Pixel XL.
Stupid question but I'm guessing bootloader must be unlocked first correct?
Denton.S said:
Stupid question but I'm guessing bootloader must be unlocked first correct?
Click to expand...
Click to collapse
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I was afraid you were going to say that. For one brief, glorious moment I thought I could get rid of adds without having to deal with this damn locked bootloader. My own mistake for getting the phone from EE direct. Thanks dude, much appreciated though
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Flapjack said:
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Click to expand...
Click to collapse
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Choose an username... said:
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Click to expand...
Click to collapse
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
So install just boot.img from twrp and flash magisk.
Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
Either do what WesTD says or find a SuperSU uninstaller zip (i think there's one around), or wipe system and reflash the ROM
Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
Click to expand...
Click to collapse
Good stuff. Thank you!
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
AnonVendetta said:
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
Click to expand...
Click to collapse
Could you say which problems you had with Magisk?
If you had f2fs then of course. But usually Magisk works as it should and has the module system which is very useful too.