I have a Samsung S4 with Android 4.3 and CWM. It was rooted with CF-Auto-root.
I decided to update SuperSU to the latest version 2.0.
1. First I activated the cleanup function from the SuperSU menu to be able to reinstall it from Google play.
I downloaded and installed it. It displayed "The SU library needs to be updated" then it displayed "How would you like to install the SU binary?". I choose TWRP/CWM button because I have CWM.
During automatic reboot into CWM recovery it installed something and then rebooted normally.
It didn't work. SuperSU displayed "The SU library needs to be updated" again.
2. I chose "Normal" button in SuperSU when it asked for binary install.
It failed to install again.
3. I downloaded SuperSU zip package (UPDATE-SuperSU-v2.00.zip), booted to CWM recovery and installed the zip file.
After I rebooted and tried to run SuperSU - it didn't work. It displays "The SU library needs to be updated" again!
Now I can't even uninstall SuperSU because it's not in the list of downloaded apps.
I can't even access its settings to do a cleanup and remove it.
How to make it work correctly or uninstall it completely?
Any suggestions?
Nasvyazi said:
I have a Samsung S4 with Android 4.3 and CWM. It was rooted with CF-Auto-root.
I decided to update SuperSU to the latest version 2.0.
1. First I activated the cleanup function from the SuperSU menu to be able to reinstall it from Google play.
I downloaded and installed it. It displayed "The SU library needs to be updated" then it displayed "How would you like to install the SU binary?". I choose TWRP/CWM button because I have CWM.
During automatic reboot into CWM recovery it installed something and then rebooted normally.
It didn't work. SuperSU displayed "The SU library needs to be updated" again.
2. I chose "Normal" button in SuperSU when it asked for binary install.
It failed to install again.
3. I downloaded SuperSU zip package (UPDATE-SuperSU-v2.00.zip), booted to CWM recovery and installed the zip file.
After I rebooted and tried to run SuperSU - it didn't work. It displays "The SU library needs to be updated" again!
Now I can't even uninstall SuperSU because it's not in the list of downloaded apps.
I can't even access its settings to do a cleanup and remove it.
How to make it work correctly or uninstall it completely?
Any suggestions?
Click to expand...
Click to collapse
I have this problem too. I have tried all three methods on cwm, trwp and philz. Anyone got a fix?
I am using broodplank's aosp 4.4.4 build.
Nasvyazi said:
I have a Samsung S4 with Android 4.3 and CWM. It was rooted with CF-Auto-root.
I decided to update SuperSU to the latest version 2.0.
1. First I activated the cleanup function from the SuperSU menu to be able to reinstall it from Google play.
I downloaded and installed it. It displayed "The SU library needs to be updated" then it displayed "How would you like to install the SU binary?". I choose TWRP/CWM button because I have CWM.
During automatic reboot into CWM recovery it installed something and then rebooted normally.
It didn't work. SuperSU displayed "The SU library needs to be updated" again.
2. I chose "Normal" button in SuperSU when it asked for binary install.
It failed to install again.
3. I downloaded SuperSU zip package (UPDATE-SuperSU-v2.00.zip), booted to CWM recovery and installed the zip file.
After I rebooted and tried to run SuperSU - it didn't work. It displays "The SU library needs to be updated" again!
Now I can't even uninstall SuperSU because it's not in the list of downloaded apps.
I can't even access its settings to do a cleanup and remove it.
How to make it work correctly or uninstall it completely?
Any suggestions?
Click to expand...
Click to collapse
It's not in the the list of downloaded apps bc when you flashed " (UPDATE-SuperSU-v2.00.zip)" it made it a system/app..so therfore the delete it.. download a root explorer and delete it from system/app..
I wouldn't install 2.0 again after you delete it.. maybe try 1.94 or something a little lower and not so new
Sent from my SCH-I605 using XDA Free mobile app
lacoursiere18 said:
It's not in the the list of downloaded apps bc when you flashed " (UPDATE-SuperSU-v2.00.zip)" it made it a system/app..so therfore the delete it.. download a root explorer and delete it from system/app..
I wouldn't install 2.0 again after you delete it.. maybe try 1.94 or something a little lower and not so new
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply.
Should I delete SuperSU's data as well?
Is it in the folder "data/data/eu.chainfire.supersu" ?
as it is asked quite often, here's how you get ota with a modified stock rom.
For example, ota will fail if you have root (as it changes your boot partition slightly) or if you deleted some preinstalled apps (e.g. chrome browser). OTA script always checks the signatures of your running rom and the ota update. If they don't match, it will fail.
An unlocked bootloader does not prevent ota from working!!!
requirements: a backup of a 'clean' stock rom
So if you want to update perform the following steps (edit: you can find a second and easier method at the end of the post)
1. boot twrp
2. backup everything to be safe (boot, recovery, system, data) if something goes wrong
3. restore 'clean' stock boot partition and recovery partition
(4. if you changed something in 'system' restore system as well)
5. boot tablet
6. download and install ota - it should succeed
7. boot twrp and restore data again if needed
(8. root again with magisk)
good to know:
if you restore partitions, make sure they are from the same build! if not, tablet might not boot or ota will fail again.
if you are rooted, you can use the the backup of boot created by the magisk script (-->/data/stock_boot_<sha1>.img.gz)
if you don't have a backup, try to get hands on a stock rom and flash the required partitions manually (e.g. fastboot flash boot.img etc..)
good luck
(if anyone knows a better way, let me know and i will add it here)
edit: @MarkAllen provided this method which is far more simple (but which unfortunately has never worked for me by now).
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser and Magisk manager from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
MarkAllen said:
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
Click to expand...
Click to collapse
great to hear...
using the uninstaller alone has never worked for me...it always aborts...sometimes it complains that some files are missing or were changed, the recovery partition doesn't match the expected one, etc...
mostly i can't remember which things i've done to the rom/system.
but again, good to know that magisk uninstaller works, it definitely is less complicated and time consuming.
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.
Hello friends. Yesterday my redmi note 4x snapdragon (mido) showed a strange problem. I was using phone normally and then a notification popped out from magisk. It was about the updates available for both - magisk manager and magisk. I first updated the manager from the app itself by clicking on 'install'.
But after it finished installing the magisk manager, when it reopened it showed that magisk was not installed!
Then I check my root applications (greenify, mixplorer) and they also were not getting root access. Neither There was a prompt for granting root acess.
I checked my root status from the root checker app from playstore and it showed - 'root access available but not properly installed'
Please suggest me what should I do to update magisk or get magisk working back.
Other details-
Rom - aosp extended official 6.3 pie treble
Kernel - Franco kernel r20
Previous magisk installed- 18.00
New available magisk - 20.3
New magisk manger that I updated - 7.5.1
Everything was working fine on my device previously.
Please help me guys.
Thanks in advance.
Solved the issue!
AviralSri said:
Hello friends. Yesterday my redmi note 4x snapdragon (mido) showed a strange problem. I was using phone normally and then a notification popped out from magisk. It was about the updates available for both - magisk manager and magisk. I first updated the manager from the app itself by clicking on 'install'.
But after it finished installing the magisk manager, when it reopened it showed that magisk was not installed!
Then I check my root applications (greenify, mixplorer) and they also were not getting root access. Neither There was a prompt for granting root acess.
I checked my root status from the root checker app from playstore and it showed - 'root access available but not properly installed'
Please suggest me what should I do to update magisk or get magisk working back.
Other details-
Rom - aosp extended official 6.3 pie treble
Kernel - Franco kernel r20
Previous magisk installed- 18.00
New available magisk - 20.3
New magisk manger that I updated - 7.5.1
Everything was working fine on my device previously.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
So friends, i figured out the solution myself. And I am describing it here in case anyone faces such a problem.
First of all, i forgot to mention one strange thing - while i was updating the magisk manager to new 7.5.1 version from the manager itself, during its installation, i got 2 prompts from google play store which said that i should not install this app as it is not a trusted application. But i clicked on "Install Anyway" both the times and it installed.
After then, when i opened the updated maanger, it showed that magisk is not installed (the new manager app also took some time greator than usual, on its first launch). And then the root access went from everywhere on my device.
Then i thought of uninstalling the magisk from flashing the Magisk-uninstaller-zip-file and then installing the magisk-v-18.zip again, but after searching for some time about uninstalling the magisk, i came to know that there are greater chances of my device going into a bootloop.
For one last time, i tried this - uninstalled magisk manager 7.5.1. Then installed MagiskManger 7.4.0 again. And when i launched it, it showed me Magisk-v18 installed!. Also the app showed me that updates are available for both - manager and magisk. App also showed the superuser menu, Magisk Hide menu. I thought that the problem was solved. But quickly i found that still other root apps were not working. When i reopened the Magisk-Manger-7.4.0, it displayed a message - "A addition setup is needed for root to work". But i did not update from there. Instead i followed a safe path -
Solution - 1. Download official Magisk-20.3 and copy in your phone's internal storage.
2. Then copy the original unaltered boot.img of the rom you're using in your internal storage.
3. Boot into TWRP recovery. Go into "install", and select "install image". Then select your boot.img and swipe to flash.
(Here, i did not wipe anything before flashing. Just flashed the img file over)
4. Reboot to your system. Now your android be cleanly unrooted.
5. Again reboot to TWRP. Select "install", and select and flash the Magisk20.3.zip file and reboot to your system.
Voila!!! Here you go! Your system is now properly rooted with latest magisk!
Thanks!
Hi there, I'm having trouble to find respective command to use in updater-script which would disable an application when running installation in TWRP recovery. I'm aware I could remove the app files/folders, but would like to try first disabling it. Is there such an option?
@Rejerf
When in recovery mode, the phone's Android OS and all its services/apps aren't loaded means not running. So no need to disable services/apps.