Related
Hi I have a rooted Nexus 7 and wanted to keep root when updating. I already have SuperSU and wanted to know what is the best way to keep root when updating. Should I use SuperSU Survival mode or download Root Keeper to keep root?
Are there any conflicts having/using both at the same time? Any advice or info on this would be great.
Thanks
randomvector said:
Hi I have a rooted Nexus 7 and wanted to keep root when updating. I already have SuperSU and wanted to know what is the best way to keep root when updating. Should I use SuperSU Survival mode or download Root Keeper to keep root?
Are there any conflicts having/using both at the same time? Any advice or info on this would be great.
Thanks
Click to expand...
Click to collapse
All I can tell you is Voodoo OTA Rootkeeper has worked great for me. Restored root with no problems after 4.2 update.
On my system - however - root causes lag on multi-user that makes it unusable, even with updated SuperSU.
So I am back to being temporarily unrooted because multi-user is more important to me than root.
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
steevp said:
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
Click to expand...
Click to collapse
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
rmm200 said:
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
Click to expand...
Click to collapse
Hmm I didn't experience anything like that, but I only played with multi-user for a few minutes then I deleted the secondary user.
steevp said:
Just install the latest CWM recovery
It gives you the option to fix the permissions of the su binary after installing an update so you can keep root.
Click to expand...
Click to collapse
I am running the stock ROM as i want to receive the updates and have the standard google recovery and do not have CWM installed. My bootloader is unlocked and rooted that's it. I am not using multiuser on my Nexus 7. I think I'll use Root Keeper and keep SuperSU survival mode off.
randomvector said:
I am running the stock ROM as i want to receive the updates and have the standard google recovery and do not have CWM installed. My bootloader is unlocked and rooted that's it. I am not using multiuser on my Nexus 7. I think I'll use Root Keeper and keep SuperSU survival mode off.
Click to expand...
Click to collapse
I'm also running the stock ROM, and updates have worked fine with CWM recovery so far.
I believe it is compatible with the stock recovery.
rmm200 said:
Well funny thing - su works fine for primary user. Only goes ape on creating or using secondary user.
Over and over, asks if /system/bin/id can have superuser permission. 20 minutes to create a secondary user...
Click to expand...
Click to collapse
I'm using SuperSU and had no issyes with setting up a secondary user.
steevp said:
I'm also running the stock ROM, and updates have worked fine with CWM recovery so far.
I believe it is compatible with the stock recovery.
Click to expand...
Click to collapse
Really, can you have a custom recovery like Clockwork manager or TWRP and still receive OTA updates?
GldRush98 said:
I'm using SuperSU and had no issyes with setting up a secondary user.
Click to expand...
Click to collapse
When I get brave - and bored - I will try uninstalling / reinstalling SuperSU again.
For right now, I am just a happy tablet user.
Hi
I have been using clockworkmod superuser on stock 4.3 with no problems. However I have just flashed a new kernel and am now getting the message that the SU binaries are out of date. I have tried re-flshing the superuser.zip with CWM but still have the same message and of course no root. Is it possible to replace superuser with the latest supersu and see if that gets my root back. If so how I do it and will I then be able to unistall the clockwork superuser app once supersu is up and running.
Thanks
Andy.
g1dtf said:
Hi
I have been using clockworkmod superuser on stock 4.3 with no problems. However I have just flashed a new kernel and am now getting the message that the SU binaries are out of date. I have tried re-flshing the superuser.zip with CWM but still have the same message and of course no root. Is it possible to replace superuser with the latest supersu and see if that gets my root back. If so how I do it and will I then be able to unistall the clockwork superuser app once supersu is up and running.
Thanks
Andy.
Click to expand...
Click to collapse
just flash the latest supersu flashable. search google for supersu, youll find it asap. its better than the latest superuser.
simms22 said:
just flash the latest supersu flashable. search google for supersu, youll find it asap. its better than the latest superuser.
Click to expand...
Click to collapse
cool wikll give it a try once flashed will it replace the current superuser app or will i have to uninstall remove it manually?
g1dtf said:
cool wikll give it a try once flashed will it replace the current superuser app or will i have to uninstall remove it manually?
Click to expand...
Click to collapse
itll add the supersu app
simms22 said:
itll add the supersu app
Click to expand...
Click to collapse
By that do you mean it replaces the superuser that is currently installed or adds it as an additional app. Sorry for the confusion but still a little confused with the various methods of obtaining root with the various superusers etc.
g1dtf said:
By that do you mean it replaces the superuser that is currently installed or adds it as an additional app. Sorry for the confusion but still a little confused with the various methods of obtaining root with the various superusers etc.
Click to expand...
Click to collapse
itll add the supersu app, youll probably have to uninstall the superuser app by yourself.
simms22 said:
itll add the supersu app, youll probably have to uninstall the superuser app by yourself.
Click to expand...
Click to collapse
Thanks for the help and will let you know how I get on once I get it downloaded and installed.
Installed the zip and everything is now working ok and I have root back. The supersu app replaced the origional superuser app so nothing to uninstall/delete.
Thanks Again
Andy.
g1dtf said:
Installed the zip and everything is now working ok and I have root back. The supersu app replaced the origional superuser app so nothing to uninstall/delete.
Thanks Again
Andy.
Click to expand...
Click to collapse
sweet
I've recently installed kitkat 4.4 on my nexus 4 with twrp recovery
I tried to flash the UPDATE-SuperSU-v1.69.zip using the recovery
the phone finish the proccess and reboot but there is still no root permission or superuser app
any help?
YTayyar said:
I've recently installed kitkat 4.4 on my nexus 4 with twrp recovery
I tried to flash the UPDATE-SuperSU-v1.69.zip using the recovery
the phone finish the proccess and reboot but there is still no root permission or superuser app
any help?
Click to expand...
Click to collapse
open the supersu app, check if it asks you to update your binaries.
simms22 said:
open the supersu app, check if it asks you to update your binaries.
Click to expand...
Click to collapse
but the supersu doesn't exist in my drawer at all
YTayyar said:
but the supersu doesn't exist in my drawer at all
Click to expand...
Click to collapse
go to the play store, download supersu, then open it after install. when it asks you to update your binaries, do it. or, try downloading supersu again(maybe it was a bad download), and flash it again.
simms22 said:
go to the play store, download supersu, then open it after install. when it asks you to update your binaries, do it. or, try downloading supersu again(maybe it was a bad download), and flash it again.
Click to expand...
Click to collapse
seems to be working,,, thanks
btw I discovered that the supersu was there in the app list in the settings but just not showing in the drawer,, however, installing it from the market solved the issue
YTayyar said:
seems to be working,,, thanks
btw I discovered that the supersu was there in the app list in the settings but just not showing in the drawer,, however, installing it from the market solved the issue
Click to expand...
Click to collapse
sweet
Hi all, I just want to share this. Regarding to Kinguser cant be replace by SuperSU, I just solve this issue. But, I want to make it clear,
I FOUND THIS METHOD ACCIDENTALLY(by experimenting).
I just got Samsung Galaxy Grand Duos I9082, with home button not functioning. So I cant root it by custom recovery, which made me use Iroot(known as Vroot), 1 click rooting app. It will root using Kinguser binary. Which will give problem to replace it with SuperSU. Then install busybox.
So I reroot my phone using KingO root which will install SuperSU v2.02. I guest this is the point where SuperSU bin get hook in device(I tried installing various ver of SuperSU without success,"Installing Failed". And KingUser give perm to SuperSU using KingO root method.
So I go into SuperSU, install as system, reboot, install custom recovery, install SuperSU.zip thru recovery, reboot, uninstall KingUser(it will warn this will unroot your device back to normal, i just ignore and proceed), and this will erase SuperSU app too, but I guest it leave the binary installed. And again I reinstall SuperSu in normal way, with success.
And again, I'm not telling the best solution, just want to share what I've done. Hope this will help someone.
Good Day
I try to replace King User with the Terminal Emulator Method, and King User gone, but it unroot mi device
I have a Samsung i8200L.
After, I re-root my device (now with Kingo Root, thanks for mention it in your thread), and everything is ok, with SuperSU
Naimlaaa said:
Hi all, I just want to share this. Regarding to Kinguser cant be replace by SuperSU, I just solve this issue. But, I want to make it clear,
I FOUND THIS METHOD ACCIDENTALLY(by experimenting).
I just got Samsung Galaxy Grand Duos I9082, with home button not functioning. So I cant root it by custom recovery, which made me use Iroot(known as Vroot), 1 click rooting app. It will root using Kinguser binary. Which will give problem to replace it with SuperSU. Then install busybox.
So I reroot my phone using KingO root which will install SuperSU v2.02. I guest this is the point where SuperSU bin get hook in device(I tried installing various ver of SuperSU without success,"Installing Failed". And KingUser give perm to SuperSU using KingO root method.
So I go into SuperSU, install as system, reboot, install custom recovery, install SuperSU.zip thru recovery, reboot, uninstall KingUser(it will warn this will unroot your device back to normal, i just ignore and proceed), and this will erase SuperSU app too, but I guest it leave the binary installed. And again I reinstall SuperSu in normal way, with success.
And again, I'm not telling the best solution, just want to share what I've done. Hope this will help someone.
Good Day
Click to expand...
Click to collapse
Easiest method that worked for me!
Use es file explorer
change permision to /system/bin to rw, tick all
run updated supersu, it will ask to update su binary, use the normal option
Kinguser will ask permission from SuperSu, DENY!
Then you can successfully remove kinguser
Newyork! said:
Easiest method that worked for me!
Use es file explorer
change permision to /system/bin to rw, tick all
run updated supersu, it will ask to update su binary, use the normal option
Kinguser will ask permission from SuperSu, DENY!
Then you can successfully remove kinguser
Click to expand...
Click to collapse
I'm assuming you used SSU 2.49? As Chainfire said, he made this mostly for lollipop comparability, also for Kinguser replacements issues.
And thanks for sharing the workaround you've figured.:thumbup:
Sent from here to there
Naimlaaa said:
I'm assuming you used SSU 2.49? As Chainfire said, he made this mostly for lollipop comparability, also for Kinguser replacements issues.
And thanks for sharing the workaround you've figured.:thumbup:
Sent from here to there
Click to expand...
Click to collapse
I didn't figure it out. it just worked for me!
Newyork! said:
I didn't figure it out. it just worked for me!
Click to expand...
Click to collapse
Maybe someone will need it later, lucky them found an easy and more practical way.:thumbup:
Sent from here to there
Hope this will work
Worked on Galaxy S3 NEO ( GT-I9300I ) Android 4.4.4
The Steps that worked for me are as follows:
Start from HERE
1. Same steps untill SuperSu installed
2. When SuperSu launched itself (or you can launch it manually ) , it
will ask to update SU Binary, Click Normal.
3. Wait until SuperSu says other user management app detected (in my
case) and will ask you to remove it. Click cancel ( very important ).
4. When you Click Cancel, it will say Binary updated Successfully. And
will ask you to Reboot or OK. Click OK ( very important ) and not to
Reboot.
5. Now SuperSu will open normally but KingUser app will still be present
( in my case).
6. Now go to Settings in SuperSu App and Go to Clean Up options and
there you will find an option to remove other User Managemnt apps, just
click the option and Boom SuperSu will remove it completely from your
System.
Hope this will work for someone else also.
2nd Method:
Just simply install SuperSu from Play Store and follow the above steps
from Number 2 onwards. (Confirm if it works for you)
Credit to : Chainfire and MrW0lf
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
maraschino said:
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
Click to expand...
Click to collapse
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Just updated mine via app , after reboot there was no signal , no simcard ,no imei dont panic reboot one more time ,and everything is working as usual.
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
maraschino said:
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
Click to expand...
Click to collapse
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
KOLIOSIS said:
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
Click to expand...
Click to collapse
Thx for info
I always update through TWRP. Just updated. Since I always choose the hide magisk option replacing it with a random name I uninstall the app real quick before I reboot to recovery. Used to be if you didn't you would end up with two apps installed. Don't know if this is still an issue or not. Either way all your settings will still be there. I uninstall the app, reboot to recovery, flash Magisk. Boot back into the OS, all my settings are already there, so the only thing I have to do is rehide Magisk.
Do this update fix the charge problem when the device is off?
ELGeKo24 said:
Do this update fix the charge problem when the device is off?
Click to expand...
Click to collapse
Didn't fix it for me.
OS 9.0.7.
TWRP 3.2.3-9
Magisk v18
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
I usually start over.
I flash a virgin boot age to both slots.
Reboot with TWRP
Install TWRP zip
Install ElementalX and Magisk zips.
Change slots and reboot recovery
Install ElementalX and Magisk in this slot.
I have the same OS version and kernels etc flashed in both slots.
lostunsunghero said:
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
Click to expand...
Click to collapse
Or you can also disable the Battery Optimisation for Magisk
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
What is the recommended install suggestion? Only Zip or with Boot image patch?
Calvin1997 said:
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
Click to expand...
Click to collapse
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
bladestonez said:
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
Click to expand...
Click to collapse
You're right. If tried the safetynet check on the new one, and after that the new one was removed. Completely strange. I hope someone here knows what to do
No problem here just selected install then used recommended.
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
So you just did the direct install option? Also are you running magisk with or without TWRP?
Calvin1997 said:
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
Click to expand...
Click to collapse
This is what I get when I install from magiek manager.
Yes with TWRP