Hello
I have recently decided to hard reset my tab. I backs up everything with titanium backup (I had root at that time). But after that I thought if I hard reset with root, then my tab will malfunction. So I UNrooted it.
After hard reset I cannot root like before. Kingroot keeps failing to root. When I looked /system/bin and /system/xbin (with es explorer) there is a file named 'su'.
But I cannot get root access. I also cannot root again.
What sholud i do. Any help would be appreciated
alnasnasu said:
Hello
I have recently decided to hard reset my tab. I backs up everything with titanium backup (I had root at that time). But after that I thought if I hard reset with root, then my tab will malfunction. So I UNrooted it.
After hard reset I cannot root like before. Kingroot keeps failing to root. When I looked /system/bin and /system/xbin (with es explorer) there is a file named 'su'.
But I cannot get root access. I also cannot root again.
What sholud i do. Any help would be appreciated
Click to expand...
Click to collapse
What tab?
alnasnasu said:
Hello
I have recently decided to hard reset my tab. I backs up everything with titanium backup (I had root at that time). But after that I thought if I hard reset with root, then my tab will malfunction. So I UNrooted it.
After hard reset I cannot root like before. Kingroot keeps failing to root. When I looked /system/bin and /system/xbin (with es explorer) there is a file named 'su'.
But I cannot get root access. I also cannot root again.
What sholud i do. Any help would be appreciated
Click to expand...
Click to collapse
You didn't unroot with the correct method, you left the su binaries. You still have the su binaries in system so all you should need now is the root management app, either the kinguser app or the SuperSU app, SuperSU is the better one of the two.
If you have custom recovery you can flash the SuperSU.zip in recovery, then reboot, open SuperSU and update the binaries and that should do it for you.
Or
You can search for the Kinguser APK and try installing it, I recommend SuperSU if you can it to work though, Kinguser doesn't work as well as SuperSU with some of the root apps.
If none of that works, try flashing the stock firmware and then start over from scratch with rooting the device again.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You didn't unroot with the correct method, you left the su binaries. You still have the su binaries in system so all you should need now is the root management app, either the kinguser app or the SuperSU app, SuperSU is the better one of the two.
If you have custom recovery you can flash the SuperSU.zip in recovery, then reboot, open SuperSU and update the binaries and that should do it for you.
Or
You can search for the Kinguser APK and try installing it, I recommend SuperSU if you can it to work though, Kinguser doesn't work as well as SuperSU with some of the root apps.
If none of that works, try flashing the stock firmware and then start over from scratch with rooting the device again.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Well I used kingroot but I havnt had much progress.
It always stops at some percentage and reboots. After that when I open kingroot, it continues with percent it had stopped and tell root failed.
After doing this some days later I got notification from kingroot "root permission exception. Recommend restore immidietly." (I don't remember correctly).
Note :- I don't have any custom recovery. It always shows my tab is not supported.
My tab is iball slide 3g q7218
Kingroot and kinguser are same. Isntit?
alnasnasu said:
Well I used kingroot but I havnt had much progress.
It always stops at some percentage and reboots. After that when I open kingroot, it continues with percent it had stopped and tell root failed.
After doing this some days later I got notification from kingroot "root permission exception. Recommend restore immidietly." (I don't remember correctly).
Note :- I don't have any custom recovery. It always shows my tab is not supported.
My tab is iball slide 3g q7218
Kingroot and kinguser are same. Isntit?
Click to expand...
Click to collapse
Kingroot is the app that roots the device but you should also have an app that manages root permissions called Kinguser which serves the same purpose as Superuser/SuperSU. When you use the Kingroot app, it roots the device by injecting the su binaries in /system/xbin and then it should install Kinguser as your root permission manager.
This is similar to using the other rooting apps to inject su binaries,and then installing SuperSU to use those binaries.
What I'm telling you is using Kingroot isn't going to work because what it does is inject the su binaries in system, you already have the su binaries so Kingroot can't do what it does, that is why it fails.
What I'm telling you is that since you still have the SU binaries, you don't need Kingroot, you need the root management app that uses the su binaries, either the Kinguser(not Kingroot)app or the SuperSU app, preferably SuperSU. This will allow you to once again use your root permissions.
If you can't get Kinguser or SuperSU installed then you'll have to flash your stock firmware to remove the su binaries from system. Then you'll be able to start over with using Kingroot and it should work again.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
If you can't get Kinguser or SuperSU installed then you'll have to flash your stock firmware to remove the su binaries from system. Then you'll be able to start over with using Kingroot and it should work again.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Does installing stock require custom recovery or root or unlocking bootloader or any such things
alnasnasu said:
Does installing stock require custom recovery or root or unlocking bootloader or any such things
Click to expand...
Click to collapse
No, to simplify this.
Do a Google search for:
"Return to stock (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, to simplify this.
Do a Google search for:
"Return to stock (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
If I go to stock will I lose any data
alnasnasu said:
If I go to stock will I lose any data
Click to expand...
Click to collapse
Probably
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Probably
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Give me step by step instructions
alnasnasu said:
Give me step by step instructions
Click to expand...
Click to collapse
I just told you to do a Google search for:
"Return to stock (your model number)"
That will find what you need if it's out there.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I just told you to do a Google search for:
"Return to stock (your model number)"
That will find what you need if it's out there.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Google search shows nothing based on my device
alnasnasu said:
Google search shows nothing based on my device
Click to expand...
Click to collapse
Then do what I said earlier.
Do a Google search for:
"Kinguser APK"
Install that
Or
Do a Google search for:
"SuperSU apk"
Install that
One of them should work, install Kinguser and then convert to SuperSU.
If you want to know how to convert to SuperSU, do a Google search for:
"Convert Kingroot to SuperSU"
Sent from my SM-S903VL using Tapatalk
If I go to stock will I lose any data
Click to expand...
Click to collapse
Probably
Click to expand...
Click to collapse
Hey flashing to stock ROM worked.
I rooted successfully.
But i didnot lose any data from internal storage (although i lost my apps but fortunately i have a backup).
Is it the problem of flashing or is it normal
alnasnasu said:
Hey flashing to stock ROM worked.
I rooted successfully.
But i didnot lose any data from internal storage (although i lost my apps but fortunately i have a backup).
Is it the problem of flashing or is it normal
Click to expand...
Click to collapse
It's normal, usually data doesn't get wiped when flashing stock unless the flashed file upgrades/downgrades bootloader, locking/unlocking bootloader usually wipes data also.
Sent from my SM-S903VL using Tapatalk
Thanx for the information.
Now should I convert from kinguser to supersu or stay with kinguser itself
alnasnasu said:
Thanx for the information.
Now should I convert from kinguser to supersu or stay with kinguser itself
Click to expand...
Click to collapse
Kinguser has issues with some root apps, SuperSU is what you need if you can get it successfully installed, some devices give trouble trying to convert to SuperSU, many of them bootloop after installing SuperSU.
There's a few different ways to get converted, search for them and try the methods that have worked best on your same brand(manufacture) of device.
Sent from my SM-S903VL using Tapatalk
Related
I rooted my wife's Inspire 4g using SuperOneClick and all went well...busybox and Superuser were installed on the phone. I enabled non-market apps and even installed a few but today I dl'd Titanium backup and attempted to backup her stuff so I could proceed with modded roms and the root permission was denied and Superuser is missing. I dl's root checker and there is no root or busybox now....any help would be appreciated
Thank you !!!
P.S. Can I just use SOC again to try and re-root the phone or is there something else that im missing going on?
Not sure if this will work, but it's worth a shot. Use ROM Manager to download and install the latest Super User (Download ROM>>Extras). If ROM Manager doesn't work either, you can just download the latest SU from my dropbox here. It's a .zip file that you flash in recovery mode.
henrybravo said:
Not sure if this will work, but it's worth a shot. Use ROM Manager to download and install the latest Super User (Download ROM>>Extras). If ROM Manager doesn't work either, you can just download the latest SU from my dropbox here. It's a .zip file that you flash in recovery mode.
Click to expand...
Click to collapse
+1
OP, once you get Su on there, you may be able to get busybox on by way of titanium backup. It's my assumption that the two are separate entities... Getting Su doesn't automatically give you busybox, I don't think, but TiBU has an option for installing a "known working busybox," after you push its "problems" button, but you need to get Su on there first, I would think.
Someone please correct me if I'm wrong, but doesn't SuperOneClick only provide temporary root? Once you reboot root is gone. Use acehack kit or bubbys simple one click for permanent root
Sent from my Inspire 4G using XDA App
cdshepherd said:
Someone please correct me if I'm wrong, but doesn't SuperOneClick only provide temporary root? Once you reboot root is gone. Use acehack kit or bubbys simple one click for permanent root
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
You are correct. SOC on;y provides temp root. No S-Off is attained so no rom can be flashed...
cdshepherd said:
Someone please correct me if I'm wrong, but doesn't SuperOneClick only provide temporary root? Once you reboot root is gone. Use acehack kit or bubbys simple one click for permanent root
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
I can confirm this 100%. Before I rooted my phone with the ace hack kit, I used soc to enable installing from unknown sources. It temp rooted my phone, also installing busybox and su. Once I rebooted my phone, it was as stock as can be again, with bb and su gone. This is normal for soc op, since it doesn't have the ability to perma root the phone.
Sent from my Desire HD using Tapatalk
just use hack kit or flash rooted rom after one click. hack kit is much better with more options and so easy now with 11
Hello!
So here's the deal: yesterday I decided to try out CM10.1 on my Nexus S. Being my first time rooting this phone all went well and I managed to flash the rom mostly without any problems. But my main concern is that after running root checker I got a message that my device isn't properly rooted... I did it just because I tried using ES file explorer in its root settings in order to delete a gallery2.apk file in system, which resulted in an error.
It's strange because I flashed the superuser zip before the rom and as far as I know CM10.1 comes with SU installed in it initially... Otherwise the ROM works perfect.
Do I need to flash everything from the beginning, doing another factory reset/wiping the cache? So far I've tried just to flash the superuser.zip from recovery (running 6.0.2.5 CWM recovery as far as I remember) and it didn't appear to root the device, although it said it installed successfully in the recovery. It may be something to do with the recovery or SU version? Any help is much appreciated!
Sent from my Nexus S using xda app-developers app
it's a problem about ES,
you should go to the settings and enable the root mode.
Jhyrachy said:
it's a problem about ES,
you should go to the settings and enable the root mode.
Click to expand...
Click to collapse
Yeah I know, tried that and ES said this feature cannot run on your phone... And the app doesn't appear in the superuser app either. Nothing does in fact. xD
I am having some difficulty rooting my One S after the jelly bean update. I was rooted prior to the update, but relocked and went back to stock for the OTA; now I'm getting the itch again, and wanted to root my phone, but I'm getting some strange issues with both supersu and superuser flashable zips.
I've unlocked the bootloader (again) and installed TWRP using Hasoon2000's toolkit. Everything went according to plan, so I carried on and pushed supersu using the toolkit. This is where the fun begins. TWRP reports a successful install, supersu is there, but I don't actually have root. It appears that I do, supersu asks for permission, but any root requiring actions fail.
I've tried flashing superuser, and supersu from the XDA thread, but to no success. Root Checker comes back successful too. The superuser.apk is in /system/app, but there is no su binary in /system/app, which is where I thought it lived.
Installing busybox or updating the su binary with supersu cause the device to hang for a second, then restart. Updating the binary using the superuser app reports success, but nothing happens.
I'm sure I'm missing something obvious, but I just can't see what and I'm more than a little puzzled. Anyone have any ideas/seen anything like this before?
I've found the su binary, it's in /system/xbin/ Is this normal? I thought it should go in /system/app, or is that just the supersu apk?
Had same problem. Download superuser zip from superuser home page. Flash in recovery and it will work
There is an issue with SuperSU 0.99 app so you need to flash superuser instead
Skickat från min HTC One S via Tapatalk 2
Are you S4 or S3?
Sent from my HTC One S using xda app-developers app
tominozh said:
Are you S4 or S3?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
My self was on s4 and got same issue
Skickat från min HTC One S via Tapatalk 2
Hello,
I have rooted my phone, flashed TWRP 2.6.0.0 and CM 10.2 with the All-in-One Toolkit. Everything worked fine.
Then I installed the SUPER SU App from Chainfire and updated the Binary on the "normal" way. After that I uninstalled the app.
Today I wanted to install a newer version of TWRP. I used the GooManager. The download worked fine and the device rebooted. I can use the phone and I get into Bootloader but when I want to go to Recovery the device reboots and reboots....
My first thought was, that I don't have Root anymore because I uninstalled the Super SU App from Chainfire and I don't get any notifications when I start a app that needs root and the built in Super SU in the settings doesn't make any logs since some days. But Root Checker says that my device is rooted and for example Titanium Backup works fine although it's not in the list of apps with Super SU.
What can I do? Maybe trying to install the recovery with the GooManager again or new Rooting and Recovery installing with the Toolkit?
Sincerely,
May be you should flash back twrp 2.6.0.0 which was working for your phone and reinstall super su
I tried to root without the toolkit. I followed all steps and everything worked fine. But when the device rebooted after rooting I stopped in the bootscreen. I'm able to get into CM and use the phone without problems, but now the root is completely gone!
Can anyone help? I really don't know what to do now.
Edit: So, after rooting I have a Super SU app installed, but it's not able to update and not working...
Can you try with the twrp from this link:
http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-ville-selinux.img
and root again
Sent from my One S using xda app-developers app
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Hevy12 said:
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Click to expand...
Click to collapse
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
ka_55 said:
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I flashed the Recovery and the SuperSU. The recovery is installed but there is no root. But I can't uninstall the installed SuperSU apk from the old try of rooting that went wrong. I only can deactivate it. Should I do this and try flashing the SuperSU.zip again?
Thanks!
Sincerely,
Edit: Problem solved with the newer SuperSU version.
When ever I am about to exit Cwm I get this error*Root Access Possibly Lost Fix Root?. There are two options yes and no. I tried both but still I get d same error.
P. S- my root is fine all root apps work perfectly
Sent from my Nexus 5 using Tapatalk
dsjd said:
When ever I am about to exit Cwm I get this error*Root Access Possibly Lost Fix Root?. There are two options yes and no. I tried both but still I get d same error.
P. S- my root is fine all root apps work perfectly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do you use SuperSU rather than Superuser? I think CWM recovery only look for Superuser, so if you have SuperSU installed it will think you aren't rooted.
Official CWM doesn't recognize the SuperSU binary. This is one of the reasons I don't recommend it, but rather PhilZ Touch CWM or TWRP.
Thanks
It helped me too, thanks
what did you guys do to fix this?
New cwm? Or Download superuser from the store and uninstall SuperSU? Can you guys please provide more details as this is driving me nuts to have to click on yes or no to fix root every time I go into Recovery. Or Should I use Twrp?
And, I'm surprised there aren't more people with this problem. Are we the only ones?
VOLTAGEROCK said:
New cwm? Or Download superuser from the store and uninstall SuperSU? Can you guys please provide more details as this is driving me nuts to have to click on yes or no to fix root every time I go into Recovery. Or Should I use Twrp?
And, I'm surprised there aren't more people with this problem. Are we the only ones?
Click to expand...
Click to collapse
Flash another recovery
or
Use Superuser
Lethargy said:
Flash another recovery
or
Stop using Superuser
Click to expand...
Click to collapse
Obviously this topic is a little more difficult for me to figure out on my own and your response even though you're trying to help me does not help. I don't know what it means to just stop using super user when I'm using supersu? Am I supposed to uninstall supersu and then install superuser? Are these the same apps? And if I do flash another recovery like team win, do I have to uninstall ClockworkMod first? I have tried to look online for an answer to this and this thread is the only one with this problem which is mind boggling the amount of Nexus 5 users compared to the five people here who are experiencing this problem. So if you can direct me to another link that has more information, that would be great otherwise I'm not quite sure how to fix this when you guys said you did it so easily.
Sent from my wondrous Nexus numeral 5
VOLTAGEROCK said:
Obviously this topic is a little more difficult for me to figure out on my own and your response even though you're trying to help me does not help. I don't know what it means to just stop using super user when I'm using supersu? Am I supposed to uninstall supersu and then install superuser? Are these the same apps? And if I do flash another recovery like team win, do I have to uninstall ClockworkMod first? I have tried to look online for an answer to this and this thread is the only one with this problem which is mind boggling the amount of Nexus 5 users compared to the five people here who are experiencing this problem. So if you can direct me to another link that has more information, that would be great otherwise I'm not quite sure how to fix this when you guys said you did it so easily.
Sent from my wondrous Nexus numeral 5
Click to expand...
Click to collapse
You replied to be as I was editing my post lol.
It only happens when you're using CWM + SuperSU, because CWM doesn't look for SuperSU, only for Superuser.
Just flash TWRP, CWM is horrible anyways. Or you could just ignore it and just press no every time. Makes no difference.
And you don't "uninstall" CWM then install TWRP. You flash it over (overwrite) CWM.
VOLTAGEROCK said:
Obviously this topic is a little more difficult for me to figure out on my own and your response even though you're trying to help me does not help. I don't know what it means to just stop using super user when I'm using supersu? Am I supposed to uninstall supersu and then install superuser? Are these the same apps? And if I do flash another recovery like team win, do I have to uninstall ClockworkMod first? I have tried to look online for an answer to this and this thread is the only one with this problem which is mind boggling the amount of Nexus 5 users compared to the five people here who are experiencing this problem. So if you can direct me to another link that has more information, that would be great otherwise I'm not quite sure how to fix this when you guys said you did it so easily.
Sent from my wondrous Nexus numeral 5
Click to expand...
Click to collapse
If your using super su, good. To change to twrp, which I recommend, just flash a twrp zip file in your current recovery. Google recovery zip collection xda.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
SuperSU
Superuser
Two different things, both are root. Think Honda/Toyota (horrible analogy)
Pick your side. I think that's what's confusing you.
Sent from my Nexus 5
Lethargy said:
You replied to be as I was editing my post lol.
It only happens when you're using CWM + SuperSU, because CWM doesn't look for SuperSU, only for Superuser.
Just flash TWRP, CWM is horrible anyways. Or you could just ignore it and just press no every time. Makes no difference.
And you don't "uninstall" CWM then install TWRP. You flash it over (overwrite) CWM.
Click to expand...
Click to collapse
I just flashed twrp and it installed fine. Thank you.
Another question, yesterday when I had CWM on my phone, I did a NAND backup which I just deleted from Root Exlporer after installing TWRP, but do I need to also delete the Clockwork folders from Root Explorer as well now?
VOLTAGEROCK said:
I just flashed twrp and it installed fine. Thank you.
Another question, yesterday when I had CWM on my phone, I did a NAND backup which I just deleted from Root Exlporer after installing TWRP, but do I need to also delete the Clockwork folders from Root Explorer as well now?
Click to expand...
Click to collapse
Yeah, you can't share backups between them as they do them differently.