Remove flashed SuperSU by uninstall from launcher - SuperSU

I flashed the latest SuperSU zip with TWRP to a MotoG 2015 with the latest Lineage. After that, I noticed that there is a native SuperSU for Lineage, which I would prefer to use.
I was not able to find a "remove" package so I uninstalled the SuperSU app from the launcher. Now I'm not sure if that really removed everything from the system because I installed it in the first place by flashing it with TWRP.
My question is, can I safely install the native SuperSU (by flashing with TWRP) or do I have to remove any files from the former SuperSU manually?

There's a full unroot option in the app. Reinstall from the Play store and run that...

Or if you have any issue with the unroot option in the app, you can always flash the unSU Script zip from here.

Didgeridoohan said:
There's a full unroot option in the app. Reinstall from the Play store and run that...
Click to expand...
Click to collapse
You're right, I did not see that before. Works pretty good, now I've installed the native SuperSU and everything works fine. Thank you.

Related

Can't Remove Superuser to Reroot

Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
One Hype said:
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
Click to expand...
Click to collapse
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
KiraYahiroz said:
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
One Hype said:
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
Click to expand...
Click to collapse
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
KiraYahiroz said:
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
Click to expand...
Click to collapse
Just did this buy with v.1.8 of SuperSU and everything worked perfect. Thank you

my phone is bricked

Firstly i have installed twrp recovery. Then I flashed superuser zip file it asked me to update binary . then i flashed updated super su zip . and now it is not starting. it is not booting . i think i have bricked my device what should i do now
Danial336 said:
Firstly i have installed twrp recovery. Then I flashed superuser zip file it asked me to update binary . then i flashed updated super su zip . and now it is not starting. it is not booting . i think i have bricked my device what should i do now
Click to expand...
Click to collapse
There's something not right in your statement. Either you misstated it or misunderstood it.
There's a difference between Superuser and SuperSU. The SuperSU is a superuser management tool. When you stated that you first installed Superuser, it tells me that you installed an app named Superuser. The Play Store does have one or more app's with the name Superuser in it.
If you stated Superuser, and meant SuperSU, then your issue may be a version conflict between the first and second SuperSU installations.
Keep in mind that the SuperSU zip is the same thing as the SuperSU free app from the Play Store. So if you can flash the zip, then I'd advise you not to install the app from the Play Store and flash it instead.
Also, keep in mind that the SuperSU Pro, from the Play Store, is only a Key that unlocks the Pro features within the free version. So always install the free version (app or zip) BEFORE installing the Pro app from the Play Store.
Sent from my SCH-I535 using XDA Free mobile app
The same thing happen to me. After installation of supersu (moto g4 ) the phone can't boot in android (only in fastboot)

How to root Dr Ketan's Latest Nougat Rom N10 for Note 5?

@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
newuxtreme said:
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
Click to expand...
Click to collapse
I thought Dr. Ketan's N10 ROM was pre-rooted with either Magisk or SuperSU. Did you not have this option in the AROMA Installer? If not, here is some help..
I personally recommend Magisk for root. It's just as easy to use Magisk over SuperSU. Each root solution has its own dedicated app as well. To root with Magisk you will need the latest root zip which is V14.0 along with the latest Magisk Manager apk.
You can download the latest Magisk Manager apk and the latest Magisk V14.0 root zip from the link below...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Here you can read and learn all about Magisk too. Once you download both the root zip and the apk, transfer both to your internal storage.
Next, download the no_verity_opt_encrypt_5.1 zip from here...and transfer it to your internal storage.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
(Its the second link from the bottom in the list)
Easy steps to root your device with Magisk..
Boot to TWRP Recovery
Select Backup and put a check in each box. That way if anything goes wrong you can restore the backup and have a working device.
Next, select WIPE - Advanced WIPE - Check both caches
Swipe to wipe both caches
Next, select INSTALL
Navigate to where you saved the root zip and select the zip.
Swipe to flash the zip
Click on the box to wipe the caches
Now, just in case, flash the no_verity_opt_encrypt_5.1 zip that you downloaded earlier.
Reboot your device. Once booted up, install the Magisk Manager apk. It will install as a normal app. Make sure you have enabled "unknown sources" in Settings - Lock Screen and Security so you can install apps outside of the Play Store.
Open the Magisk Manager app and set it up to your preference. It's very easy to use.
If you run into any issues don't hesitate to ask questions.
Good luck and happy flashing!
Sent from my Samsung SM-G955U using XDA Labs

The root permission request is no longer displayed

I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
@rovo89
@topjohnwu
https://www.didgeridoohan.com/magisk/MagiskHelp
I have added much more information.
Reinstall firmware???
LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe

Update lineageos OTA update and keep root access.

Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.
mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
ethical_haquer said:
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.
Click to expand...
Click to collapse
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
Minionguyjpro said:
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
Click to expand...
Click to collapse
I'm installing an update right now. I would imagine it works with TWRP as well, but I only recently started using it.
I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).
droidman1992 said:
I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).
Click to expand...
Click to collapse
Well, I came to the fact I have a problem with TWRP. It uses OpenRecoveryScript for OTA updates and should also run addon.d scripts after it (Magisk uses this to survive an OTA). The only problem is that the scripts should run after the OTA flash, but for me, it doesn't. So I need to manually reflash Magisk and Gapps after installing an update. My data is encrypted, but I edited the addon.d script to flash the ZIP from the external SD card.

Categories

Resources