Cant access root without kingroot. Need superSu - Galaxy S 4 Q&A, Help & Troubleshooting

What is this Whenever I uninstall kingroot I lose my root access.. I rooted my phone from CF Autoroot, means I should have SuperSu installed but whenever I tried to update binary it used to show disable knox and I did it, I completly uninstalled Knox and now whenever I try to update su binary it says installation failed. Reboot and try again.. I tried sever times but same issue Even I googled and followed dufferent method but su-binary didnt updated and I am forced to stay in kingroot :/

I lije king root

Have you tried flashing supersu.zip in recovery?

Yes, sir I tried from TWRP

It says: There is no SU binary installed, and super SU cannot install it. There is a problem. .

GDReaper said:
Have you tried flashing supersu.zip in recovery?
Click to expand...
Click to collapse
Help sir

Athakuri700 said:
Help sir
Click to expand...
Click to collapse
I think the problem is kingroot. It may prevent other superuser apps from installing properly.
If you want supersu, start from 0 (reflash stock) and root it with cf-auto-root first.

Isnt there any alternative way????

KingRoot is only useful if other methods of rooting are either unavailable or not working anymore. If you have a GT-I9505, you can do some trick to root your phone with Towelroot by downgrading kernel using the KitKat one and reflash using the stock Lollipop one right away after rooting.
My suggestion to reflash stock first (like @GDReaper said), and try Towelroot or CF Auto-Root method.
Sent from my GT-I9500

I think another way to root would be to flash TWRP and install supersu from TWRP.

I didn't like KingRoot, and found it very invasive. After it is installed, it continues to slam remote servers for no apparent reason.
KingoRoot seemed 1000 times better and their SuperUser app seems fine. However, the only way I could get SuperSU installed, was to freeze KingoUser/SuperUser and then install SuperSU, then install to system. Reboot and done. I just had to keep Kingo's SuperUser frozen to avoid any problems.
Hopefully this helps.

audit13 said:
I think another way to root would be to flash TWRP and install supersu from TWRP.
Click to expand...
Click to collapse
Audit As I earlier said.. It says: There is no SU binary installed, and super SU cannot install it. There is a problem. I flashed through TWRP

krasCGQ said:
KingRoot is only useful if other methods of rooting are either unavailable or not working anymore. If you have a GT-I9505, you can do some trick to root your phone with Towelroot by downgrading kernel using the KitKat one and reflash using the stock Lollipop one right away after rooting.
My suggestion to reflash stock first (like @GDReaper said), and try Towelroot or CF Auto-Root method.
Sent from my GT-I9500
Click to expand...
Click to collapse
Brother.. I am in Kitkat only. And I used CF Autoroot to root my device

Did you try removing all traces of previous supersu installations before flashing via TWRP? Which version of supersu was flashed through recovery? The phone has the latest releast of TWRP?

@Athakuri700,
Your phone model?
Sent from my GT-I9500

Its s4 gt-I9505 kitkat 4.4.2 baseband XXUGNH6.. yes the TWRP is of latest one as I flashed from TWRP Manager app..

Not sure if it makes difference but try reflashing twrp using odin, then flash supersu.

Related

SuperSu Binaries are not installed and SuperSu cannot install these binaries.

Hello there, I've been looking around online looking for a way to solve my SuperSu problem, but I haven't found a solution yet I was wondering if you guys could help me.
I installed my root using Odin and CF-ROOT I then realized I had both, Kingroot and SuperSU. Kingroot was the one with the root authorization and SuperSU did not have root authorization. Before I did anything SuperSU used to say "Binaries need to be updated use Normal Or TWRP/CWM," but after I used "Replace kingroot with supersu" It now says "No binaries are installed and SuperSU cannot install them." I'VE tried many methods to solve this. By the way I'm new to this stuff.
Methods used: About Device:
1. Flash updates binaries. 1. Model number: SM-G900T
2. Flashed SuperSU update. 2. Android version: 4.4.2
3. Tried to eradicate SuperSU.
SuPeRsUpRoBlEmS said:
Hello there, I've been looking around online looking for a way to solve my SuperSu problem, but I haven't found a solution yet I was wondering if you guys could help me.
I installed my root using Odin and CF-ROOT I then realized I had both, Kingroot and SuperSU. Kingroot was the one with the root authorization and SuperSU did not have root authorization. Before I did anything SuperSU used to say "Binaries need to be updated use Normal Or TWRP/CWM," but after I used "Replace kingroot with supersu" It now says "No binaries are installed and SuperSU cannot install them." I'VE tried many methods to solve this. By the way I'm new to this stuff.
Methods used: About Device:
1. Flash updates binaries. 1. Model number: SM-G900T
2. Flashed SuperSU update. 2. Android version: 4.4.2
3. Tried to eradicate SuperSU.
Click to expand...
Click to collapse
Are you on TW stock rom or Custom Rom? do you have recovery flashed?

Lost root after 1-2 days

I recently got a Galaxy S5 (SM-G900T with LMY47X.G900TUVS1FOJ4).
I grabbed chainfire autoroot and flashed it with the Odin 3.10.6 that came with the CF file. It successfully rooted the phone. I installed Titanium Backup and restored all the stuff I wanted from my old device.
I've been using the device for 1-2 days now and lost root. I opened TB and it says I'm no longer rooted. I confirmed this by downloading a root checker and it also says I'm not rooted.
According to TB, I had BusyBox for root. There was no application icon nor was it in my list of installed applications. When I used chainfire's autoroot on my S4, it installed a super user program that I could open from my app list.
I would really like to continue using Titanium Backup. Does anyone know how I can gain root access again? I already messed it up once by reflashing the autoroot. This caused an infinite bootloop and I eventually got out of it by doing a factory reset. I've returned my S4 to T-Mobile and don't want to soft brick my phone again.
Thanks.
Anyone have any suggestions of how I can reroot my phone?
If you successfully used cf autoroot then that's not the issue.....My money is on a deleted or disabled or un-updated super user app.... this is what will give you (or prevent you from having) root access to your device.
http://i.imgur.com/rVnFwJM.jpg
Using supersu v2.65 works well for me
whynoteel said:
Anyone have any suggestions of how I can reroot my phone?
Click to expand...
Click to collapse
Some days ago I get same problem ( lost root ) because i use supersu v2.67 on cm13 for sg s5 : g900f
therefore, after installed cfroot you can use twrp 3.0.0.0 as custom recovery
Then , Download. & update supersu to v2.65 by using twrp recovery ZIP version
Thanks i'm waiting for a reply

Stuck at supersu binary

Hi everyone,
I tried to root my G2 on KK with IOroot. After flashing supersu didn't work. It asks to update supersu binary and when i try to udate binary, it fails. I have also tried updating binary after updating supersu app from playstore but same happened. Now i can't remove supersu from phone as it is a system app now. How can i root my phone properly at this stage?
Kindly help
ali.akbar01 said:
Hi everyone,
I tried to root my G2 on KK with IOroot. After flashing supersu didn't work. It asks to update supersu binary and when i try to udate binary, it fails. I have also tried updating binary after updating supersu app from playstore but same happened. Now i can't remove supersu from phone as it is a system app now. How can i root my phone properly at this stage?
Kindly help
Click to expand...
Click to collapse
Try flash newest beta from SuperSU zip or try new better Magisk and after flash not forget to bump with blastagators bumpscript
Zero_Rik said:
Try flash newest beta from SuperSU zip or try new better Magisk and after flash not forget to bump with blastagators bumpscript
Click to expand...
Click to collapse
I don't have any custom recovery installed on my phone, i can't flash what u mentioned. Kingroot also fails

Problem rooting my S5 phone

I am trying to root my S5 G900F phone by flashing through odin, but the SuperSU keep says that su binary was not installed. I have tried to use other rooting method like KingRoot and one click root bus was unsuccessful. I have tried to manually installed su binary through flashing in twrp but also fails. I have been seeking the solution in the web but it seems that all of the solution for the su binary not installed problem does not work for me. Is there another way to root the phone? Thanks.
Is the oem unlock in the developer options on?
The method used here is outdated (CF auto root). The current method is to first flash TWRP in ODIN, then immediately flash the SuperSU zip in TWRP.
The alternative way is to use magisk for hiding root.

[Q] Successful rooted, but /system is read only?

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

Resources