Database Info

[Q] Showcase- cant root after installing CM7

would have just asked in :
http://forum.xda-developers.com/showthread.php?t=1142872&page=67
but i don't have enough posts, and don't want to spam a bunch of useless "cool" posts to get my count up.
Anyways,I did every thing in that topic and have CM7 running fine on my Cell South Showcase. But, i don't seem to have root access superuser is there but seems to do nothing. i tried checking via the terminal with just a "su" command and got nothing. Tried Superoneclick (my go to rooter for awhile) and it just hangs at "looking for device" . and, Z4 seems to not work with 2.3.4 phones.
So is there any fix to this, or have i just hit some crazy bug?
I have seen some people allude to changing the kernel, but the last time i tried to upgrade/change the kernel on this phone i had to save it via odin

Don't you HAVE to be rooted in order to run cm7?

i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything

thenumber5 said:
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
Click to expand...
Click to collapse
Clear data on superuser app and/or uninstall/reinstall it.

Ah,I see.. yes, try above. If no. Maybe wipe and reflash?

ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?

thenumber5 said:
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
Click to expand...
Click to collapse
Yup just an app

Also:
i have already flashed via Odin back to stock once and did the whole CM7 flash again from a fully clean rom

ok, Flashed Superuser 3.0 beta 3
no go, says my SU binary is out of date, and the app crashes when it tries to update it
checked my bin and xbin, both have a "SU" file in them
in terminal when i CD in to both folders and try to run "SU" i get an error that looks like it is trying to relocate a library and failing to do so
Can i just download the new SU binary my self and manual drop it in to the folders?

well that didnt work, cant modify anything in the system folder so i cant delete that old "SU" and replace it with the one from the superuser 3.0 apk

LOL
well i got it to let me replace the SU in /bin but not in /xbin
so now i got some half confused phone, i can grate Superuser "superuser" but when it tries to update or do any thing the log says "gaining root access....fail"
i still dont know how i have have a CM7 phone that by it very nature is rooted that thinks it is not rooted

ok for anyone who cares, i just gave up flashed via odin back to stock and tried the MIUI port, worked great once i fangled MMS in to working again

I had a similar problem, at which point I grabbed stericson's busybox app from the market which allowed me to flash a working busybox which after a reboot or two and running the installer again fixed me up..there is an app called root checker that can give info on su, superuser.apk, and busybox installs
I am almost positive that when I used jrummys busybox installer our killed root access on my phone. I had superuser.apk but without busybox it was rather useless as no apps could get root. the fix was flashing busybox 1.19.0 and leaving it in xbin and letting the app do its thing once I had rebooted.. then I rebooted again and everything was fine! after bring rooted for so long I don't think I could function without it!
for others out there, my experience has been this: stay weary of the jrummy busybox installer...its never given me anything but problems...and honestly unless busybox is borked, or ya have a damn good reason to upgrade or downgrade my suggestion is to leave it! the potential problems that can arise (for me every time, using jrummy's version..3 times) can be a pain!
Sent from my SCH-I500 using XDA Premium App

i had the same issue but dont recall if it was CM7 that did it or not but i think it was.
i had to completely blow out the phone and start from scratch.
if i recall, CM7 uses a different version of SuperUser and it just want bonkers on me but completely blowing everything out reformatting and everything seemed to work.

If you're on CM7 already, you should be rooted. If not, try SuperOneClick (Google).

[Q] BusyBox Updater Breaks Root Access

There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?

I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.

Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary

[Q] Is a Partial Root possible?

Please excuse me if this has been covered elsewhere but I have done a search and can't find anything that applies to my Transformer or the problem I have.
I used Razorclaw to root my Transformer when it was on Honeycomb, and Voodoo OTA rootkeeper to retain it when I upgraded to a later version of HC. And then again when the first ICS update came out. However when the .17 OTA came out, in my haste to try and fix the problems that came with the first ICS update, I hit 'install' without thinking. I should have made sure voodoo had a fresh backup and temporarily unrooted the TF (as I had done on previous updates).
So after the update I checked with both Titanium Backup and Voodoo which indicated I did not have root. I selected the 'restore root' option in Voodoo and it then indicated I had regained root access.
So now the three apps that I had granted root access prior to the upgrade (Titanium Backup, ES File Explorer and Voodoo) still have root access, but whenever I try a new app that requires root it says I don't have root. And checking in Superuser the 3 apps above are listed as allowed, but no other requests are even logged.
So my question is how can I have some apps that require root working, yet new requests are denied? And is there a simple way to fix it? I don't want to uninstall Superuser in case that loses me root completely (and permanently) and when I try to update Superuser it fails to gain su and stops.
Edit:TF is running Stock firmware, just rooted.

Look to see if you SU in system/xbin if not look in system/bin and copy SU from there to system/xbin

baseballfanz said:
Look to see if you SU in system/xbin if not look in system/bin and copy SU from there to system/xbin
Click to expand...
Click to collapse
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...

dingbatt said:
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
Click to expand...
Click to collapse
Try running ViperMod (option 1) again to get full root.

dingbatt said:
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
Click to expand...
Click to collapse
I don't think you have root. I had same thing happen, literally almost exactly and its because I did not have proper root. Use vipermod to get root back and you'll see everything will work like normal
Sent from my Transformer TF101 using xda premium

Thank you both baseballfanz and eminembdg (I pushed the thanks button) Vipermod Option 1 did the trick. I now have full root access restored. The biggest problem I had was I couldn't find any Win7-64 ADB drivers so had to go and pull the old Win7-32 laptop out to get everything to work properly.
Still can't see why I had partial root permissions though. I thought it was all or nothing. Kind of like being a bit pregnant.

ZTE V768 (Concord) and V768G (Midnight) Development

Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!

VROOT installs a app "Superuser.apk" not Kingroot
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!

abmx7 said:
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!
Click to expand...
Click to collapse
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810

pflatlyne said:
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810
Click to expand...
Click to collapse
anything i can help with getting a recovery working?

ultravioletnanokitty said:
Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!
Click to expand...
Click to collapse
Edit: was able to root with kingoroot my bad.

i need a custom recovery for it please

replace kinguser with supersu

somebody could teach me the easiest way to replace kinguser with supersu please?

dewagame said:
somebody could teach me the easiest way to replace kinguser with supersu please?
Click to expand...
Click to collapse
Follow these simple steps:
1. Go to the Play Store and install SuperSU.
2. When SuperSU is installed, give it permission as Super User.
3. Uninstall KingUser.
4. Done.

ИΘΘK¡€ said:
Follow these simple steps:
1. Go to the Play Store and install SuperSU.
2. When SuperSU is installed, give it permission as Super User.
3. Uninstall KingUser.
4. Done.
Click to expand...
Click to collapse
hI! I try on my HUAWEI ASCEND G6 and... dont work ... is possibel that an update that Kinguser had done make it impossibel?????
I root with RootGenius_en, was ok, kinguser ask for a update, done. But Now i whant to change do SuperSu and dont work. I had permissions and every thing...
Help! :crying:

Me too
I'm trying to do this too, but I aint sure how to do it. I mean I guess if its not super necessary I can leave it the way it is. Tried this method and its a no go. I don't think the KingUser SU is letting superSU update its binaries. I already have twrp, but not sure what next. If its not necessary I'll leave it alone, but I was just wondering if theres any reason to change over or if it could even be done.
P.S This way never worked for me as superSU can't get past trying to install the binaries. I got twrp so I'm wondering if I'd have to flash it. Nothings wrong on my end are anything, but I just assumed having superSU would be better then kinguser but not really sure.

many people have this problem.
first of all, kinguser is great to root the G6, and in most cases the only working method without custom recovery,
but because it flashes kinguser.apk as system app you can't uninstall it the normal way.
the solution is to flash supersu.zip and then uninstall kinguser. this way supersu will be your systemapp.
find the files and tutorials you need on our facebook group,
we have 1500+ members, CWM + TWRP, android 4.3 + 4.4, we can root your g6 and unlock your bootloader.
but we still don't have a subforum on XDA....
https://www.facebook.com/groups/328261053999820

Must vary from device to device cause I've did all that, and it gives the message "Installing Please wait..." and then after it fails it says " Installation Failed! Please reboot and try again" and if kinguser is removed in superSU when trying to update/install the binaries it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If just upgraded to Android 4.3 you need to manually re-root- consult the relevant forums for your device."
This aint the g6 though but this thread is the kinguser replace with superSU thread. So I thought I'd post in it.
washichi said:
many people have this problem.
first of all, kinguser is great to root the G6, and in most cases the only working method without custom recovery,
but because it flashes kinguser.apk as system app you can't uninstall it the normal way.
the solution is to flash supersu.zip and then uninstall kinguser. this way supersu will be your systemapp.
find the files and tutorials you need on our facebook group,
we have 1500+ members, CWM + TWRP, android 4.3 + 4.4, we can root your g6 and unlock your bootloader.
but we still don't have a subforum on XDA....
https://www.facebook.com/groups/328261053999820
Click to expand...
Click to collapse

Install SuperSu rom magazin play.
Then instal rom lite box.
Open the app, and uninstall kinguser
easy, and it`s working.I just deleted kinguser 2 mins ago

Hum
@andruala Never worked for me that way, anytime I remove king user root gets removed. Never was able to flash superSU rom correctly because binaries couldn't get updated from superSU because root was removed once king user was uninstalled. I've heard people mention it working the way you suggested, but I've also read posts where people have a hard time getting it replaced with superSU because root gets removed when king user is replaced, which doesn't allow superSU to install the binaries correctly. Most people probably can't get the binaries installed correctly from superSU which is the same problem I had so they end up just leaving it king user. I could try whats suggested here but I very much doubt its going to work as explained from my conflict that when king user is removed, root is removed and whether you flash a SU zip or not root still aint enabled because SU binaries are nt installed correctly. So until I actually can confirm this works myself I'm gonna prob say its a no-go for me. Could be device specific but I did all this to a tee and still had problems. There was a post on freak tab where someone had the same problem. I might still try this, I just dont see it working like as said.

freestilesteve said:
@andruala Never worked for me that way, anytime I remove king user root gets removed. Never was able to flash superSU rom correctly because binaries couldn't get updated from superSU because root was removed once king user was uninstalled. I've heard people mention it working the way you suggested, but I've also read posts where people have a hard time getting it replaced with superSU because root gets removed when king user is replaced, which doesn't allow superSU to install the binaries correctly. Most people probably can't get the binaries installed correctly from superSU which is the same problem I had so they end up just leaving it king user. I could try whats suggested here but I very much doubt its going to work as explained from my conflict that when king user is removed, root is removed and whether you flash a SU zip or not root still aint enabled because SU binaries are nt installed correctly. So until I actually can confirm this works myself I'm gonna prob say its a no-go for me. Could be device specific but I did all this to a tee and still had problems. There was a post on freak tab where someone had the same problem. I might still try this, I just dont see it working like as said.
Click to expand...
Click to collapse
Yes...i`m really sorry.For me wit worked before i restarted the phone...
After de restart i`ve seen that the root is not working anymore...
Sorry for my bad.

No worries bro. Probably varies depending on how you root from device to device.
Its not your fault. No worries. I'm just thinking it varies from device to device and how you actually go about rooting . I'm also thinking that maybe if I rooted with another app/prog that it would have been easier to switch from king user to superSU. I use lookout premium security on my phone and kingroot and king user have never been flagged with any viruses so I've just left it on and running the way it is and so far so good. Other then the two errors I mentioned in the previous post king user/kingroot has been working good. I'm sure if I did a whole restore/wipe/clean and root with another program there might be a possibility to remove king user and replace with superSU but in the end I just decided to roll with king user/kingroot as I didn't feel like doing al that and its been doing its job fine.
QUOTE=andruala;58880236]Yes...i`m really sorry.For me wit worked before i restarted the phone...
After de restart i`ve seen that the root is not working anymore...
Sorry for my bad.[/QUOTE]

Well I thought about leaving kinguser sitting there on my system too until one day I installed network monitor stuff and noticed kinguser sure likes to make HTTP connections every time the Internet is available. Imagine that. Also have a look, there are /system/bin/.usr/.ku etc. hiding all over your system.

The earlier versions of Kingo Root were much better
jidanni said:
Well I thought about leaving kinguser sitting there on my system too until one day I installed network monitor stuff and noticed kinguser sure likes to make HTTP connections every time the Internet is available. Imagine that. Also have a look, there are /system/bin/.usr/.ku etc. hiding all over your system.
Click to expand...
Click to collapse
Those earlier versions were putting SuperSU binaries into the root. But now they are putting on this King User crap. Reason I say it's crap is exactly what you mentioned. As soon as I root a phone with Kingo Root, Google Search immediately tells me that it will not allow me to search for anything because "your computer or network may be sending automated queries. To protect our users, we can't process your request right now"
Good God! What the heck is Kingo Root putting onto these phones now? It sure isn't putting just su binaries in there.

Indeed. What is needed is for someone to take a vanilla phone into a cleanroom, install the mess, and report back on exactly what ended up getting put where, in order for somebody to make a "kinguser detox/.antidote" APP and/or shell scripts that would clean the mess totally back off.

don't know if it's gonna help you ( have alcatel onetouch idol 2 mini s):
i also couldn't update binaries su and had kinguser.
then i downloaded the beta version of supersu (on xda) and flashed it with my cwm. after that when supersu asked if i wanted to update, i said yes and choose normal update (not the cwm/t... one) it than updates and asked if i wanted to remove the external root apps (ie: kinguser) and voila!
(sorry English isn't my language, so don't know if i explained myself well^^)

satine01black said:
don't know if it's gonna help you ( have alcatel onetouch idol 2 mini s):
i also couldn't update binaries su and had kinguser.
then i downloaded the beta version of supersu (on xda) and flashed it with my cwm. after that when supersu asked if i wanted to update, i said yes and choose normal update (not the cwm/t... one) it than updates and asked if i wanted to remove the external root apps (ie: kinguser) and voila!
(sorry English isn't my language, so don't know if i explained myself well^^)
Click to expand...
Click to collapse
Why did you need to root with kingo if you have custom recovery?!

I rooted first then found the cwm for my phone?

satine01black said:
I rooted first then found the cwm for my phone?
Click to expand...
Click to collapse
Oh. I wasn't angry at you Was just asking.

it took me like a year to root my phone then i couldn't make it work well with kinguser, and i wanted supersu anyway, so i found that i could install manually the app with cwm .
anyway, i don't now if you can use cwm without a root?

satine01black said:
it took me like a year to root my phone then i couldn't make it work well with kinguser, and i wanted supersu anyway, so i found that i could install manually the app with cwm .
anyway, i don't now if you can use cwm without a root?
Click to expand...
Click to collapse
You can, but it doesn't really make much sense to.

Use Eroot, then try superSU installation
CVAngelo said:
Those earlier versions were putting SuperSU binaries into the root. But now they are putting on this King User crap. Reason I say it's crap is exactly what you mentioned. As soon as I root a phone with Kingo Root, Google Search immediately tells me that it will not allow me to search for anything because "your computer or network may be sending automated queries. To protect our users, we can't process your request right now"
Good God! What the heck is Kingo Root putting onto these phones now? It sure isn't putting just su binaries in there.
Click to expand...
Click to collapse
I had the same issue with my mobile, (Sony Ericsson Xperia Ray (ST18i)), I then rooted my phone with EROOT Software which installed a superuser app, then i got the .apk file of SuperSU via Bluetooth from a friend and installed it. one has to grant permission when it asks for superuser rights, then updating binary files is no longer a problem. It also asks for removal of the Superuser-app that was pushed through the EROOT software, you do that. Then I installed link2SD and link2sd pro key from google play store and converted the SuperSU app into a system-app. Now SuperSU is working perfectly again.
You both should try it!!