Since updating to Lollipop, my old method of root for this device no longer works, I flashed it in TWRP before, but that stopped working in 5.02, this time I read the only way to root would be to use CR autoroot, it worked but the SU app askes for me to update the binaries every time I launch the app, I've updated selecting normal, that was successful and rebooted, but the update binary pop-up still appears, I then selected to update using TWRP, that launched into TWRP upon reboot, the installation was a success but the pop up still hasn't gone.
Also for the record, I've unroofed and re-rooted, the problem still occurs, I've tried switching SU app to KingUser, that didn't work, I can still perform operations that require root because I'm rooted, but this pop-up will not cease, I've never used SuperSU before, my SU manager has always been KingUser (com.kingroot.KingUser)
Thanks.
Related
I'm using LG G3 D858HK, Dual Sim., Android 5.0.1 (i updated it after i rooted it). I rooted it through my computer, hence it's under a system application and cannot be uninstalled through the play store. After i updated it, many of my apps (that requires rooting) couldn't be used. Error message was no SuperSu binary installed. So i decided to unroot my phone, and i couldn't even open the SuperSu app! It says, "There is no SuperSu Binary installed and Supersu couldn't install it, that's the problem! If you updated to 5.0.1, please consult the relevant forums!". I couldn't get into recovery mode as well, i used third-party apps, and they requested for root access. I tried to reboot it into recovery mode by using the buttons and it ended up factory resetting my phone.
Any suggestions?
Oh yes, and i couldn't find the stock firmware for my model as well, hence i couldn't downgrade it, any tips?
Accidentally installed SuperUser, and disabled root access. Am I beyond repair?
Latest version Cyanogenmod 13. Moto X 2014
Background:
Today, I tried installing SuperSU using this method. Apparently it's only for LG devices, so it didn't work for me. I bootlooped.
Then, I tried uninstalling it using this script. It uninstalled most of it, and fixed the bootloop, but more problems arose. Now I don't have root access on my phone anymore. I try changing my root access settings, but nothing changes. I figure this is because the script didn't fully uninstall SuperSU, so SuperSU is still my root controller.
I did more researching on fully uninstalling SuperSU, and came across this thread. I thought the reply said installing this would remove SuperSU, but I was wrong. I installed it, and now I have superuser installed on here as well.
I can't seem to find any way to remove superuser (or SuperSU). When I go into recovery (the only way I can get root access) and remove all superuser-related files, I reboot and find everything has been reinstalled. Another way I can get root access is through ADB. When I try removing superuser through ADB it appears to work, but when I reboot everything has reappeared.
My actual question: How can I uninstall superSU and superuser and get root access back?
I've made a terrible mistake. I really regret trying to install SuperSU, and then accidentally installing superuser. Things were working okay before, I just wanted to use some SuperSU-specific apps.
What should I do? I don't have a copy of my system.img, only a copy of boot.img. Do I just need to reinstalled CyanogenMod? Or is there a way to uninstall superuser and SuperSU and regain root access.
Edit: As I was preparing to reinstall CM, I thought I should update first, so that the reinstall would go more smoothly. I updating to the latest nightly (I was one night behind), and lo-and-behold, it fixed EVERYTHING! It automatically removed superuser, and my root access works again! I am completely content now. Still, if anybody can show me how to get SuperSU to WORK that would be greatly appreciated. But I'm not sure I want to risk it.
Hi, I have been using Magisk for last one month. Everything worked fine. All my root apps worked like a charm. Today I tried to install an OTA update. For which I tried to restore stock boot image with Magisk. After Magisk showed, 'restore successful' message, I tried to install the OTA (April), but I couldn't, it kept on showing installation error.
I then tried to reboot my device but it got stuck in bootloop.
Using MiFlash Tool, I flashed back the stock ROM which restored everything including the bootloader but retained my data (user apps and settings, Magisk and other root apps were also retained.) I then updated my stock ROM with the OTA.
Then with ADB, I unlocked the bootloader and flashed the patched boot image file of April.
After booting up first time after the patch, Initially the Magisk and root checker, both showed me root access, but after a reboot, the root access was gone. The root checker now says - Root access is not properly installed on this device.
Magisk homescreen says, Magisk is Latest Version v16.0 but Magisk is not installed. On clicking the install button, it only shows two options - Download Zip only and Patch boot image file.
What should I do to get back my root access?
You have to reflash Magisk manually after every OTA update.
I have a LG 410g, I used kingroot to root the phone, then used rootchecker and it said that the root was successful, so I installed superSU, but the latest version (2.82) gives the "binaries occupied" error. I rolled back to version 2.79 and tried downloading the binaries but it always fails, and the phone's recovery mode only has one option to factory reset, so i can't install the binaries that way. I've been looking for a solution for this all day but nothing seems to work.
You'll probably have to remove Kingroot first. No, I've no idea how... You're going to have to put your Google-fu to the test.
Just thought to let you all know.
I just installed a Nexus 4 with 5.1.1 and installed Magisk v16 along with Manager v5.8.3. It offered to update to 5.9.0 which I did. All ok, it then said Magisk is not installed while current version has bumped up to v17. Cool.
Well that was it, manager hanged permanently and I couldn't even control the device with ADB, reboot shell, nothing worked.
Rebooted manually, hanged the same, could use adb shell, but impossible to do anything.
Only solution: wipe/reinstall. Maybe installing v17 manually would have helped, but I didn't bother.
To all, be careful updating to 5.9.0.