Database Users

[Q] SuperSU hidden/half enabled

I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?

DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.

That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.

DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.

simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.

Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!

DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats

WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..

[Q] SuperSU and superuser problems

Nexus 4 running CM10 nighty and faux123 kernel
fauxclock app has problem remembering settings when using superuser so previously I installed superSU then removed superuser using root explorer, all good and no problems.
recently I updated CM10 to latest nightly, and as superuser is bundled app it was installed too. so now I have 2 apps for permitting root access but here my problems begin.
Neither app would grant superuser status to apps that requested it
superuser would force close when opened
superSU would start, then try to install the superuser binary, which it could not do as it did not have root privlige
I uninstalled superSU and rebooted, now my launcher pages had all changed back to default (no widgets and stock wallpaper) but worse I had no notification bar and the softkeys where not available. Very hard to navigate the phone
Anyways after an hour I gave up trying to fix the mess I had gotten into and restored my backup from recovery.
So my question is, where did I go wrong? What is the correct procedure for updating the ROM - other than a clean install
Prehaps I should have reinstalled superuser and removed superSU prior to the update?
Any pointers would be appreciated.
Thanks
Rumple
EDIT:
Found some good info on this in the CM10 thread, maybe I should have started there instead of searching all the superSU threads on XDA
problem is now fixed

CWM Installation Fails - Ouya (!) Screen

I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.

Thanks for posting this, I will have time to try it to tomorrow, hopefully it fixes this issue for me as well!!

boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload Mod Collection 4.0
Open Xposed Framework and check Mod Collection 4.0 as a module
Open Mod Collection 4.0 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open Mod Collection 4.0 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
Where can I download Mod Collection 4.0 or did you mean Mod_Collection4Ouya.3.6.apk?

Thanks I will try this.
Sent from my GT-I9100 using xda app-developers app

@Toxic_Dragon - you are correct. I meant ModCollection4Ouya version 3.6. I've updated the original post. Thanks!

boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
It didn't work for me.
Sent from my GT-I9100 using xda app-developers app

I had issues with ADB and fastboot until i changed the drivers for the ouya manually for every step in the device manager.

THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:

CheeseMcGee said:
THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:
Click to expand...
Click to collapse
What exactly did you do as I can't get this to work.
Sent from my GT-I9100 using xda app-developers app

robinscp said:
What exactly did you do as I can't get this to work.
Click to expand...
Click to collapse
I had used a different method to root and install CWM, but in order to fix the problem, I literally followed every step in order starting with sideload One Click Root. It was redundant and un-necessary, but it produced the results in the end by following step by step.

[Q] Changing Superuser

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

Rooted, but not rooted

Hi!
I am new to Android, been using iOS since 2007 and now I want to root my LG G2.
I used ioroot10 (also tested with ioroot6), and it seems to work nice until i f.ex:
1) Open a app that need root access, and normally asks for permission, like Titanium. I don't get any question about permisson.
2) TWRP: Try to backup, but the mobile reboots with a dead android icon.
3) Open the Superuser-app, but there are no apps listed there. When I try to use the Binary Updater it fails on: "Making sure new su works".
Any help?

Hi,
Take a look here instead: http://forum.xda-developers.com/showthread.php?t=2448887.
It works flawlessly.

install SuperSu from play store. once you instal it will automatically remove superuser.... now supersu should now ask you for permission.

Damasterjj said:
install SuperSu from play store. once you instal it will automatically remove superuser.... now supersu should now ask you for permission.
Click to expand...
Click to collapse
Thanks, worked great!
But TWRP still gives me reboot with dead android icon when trying to backup.

janfredrik said:
Thanks, worked great!
But TWRP still gives me reboot with dead android icon when trying to backup.
Click to expand...
Click to collapse
I'm not using TWRP. maybe somebody can help you with that