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..
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
Hi
I am using miui v5 4.3.x
Since it still does not have a multirom supported kernel, I decided to install ubuntu touch by their official dual boot method. Everything went fine but it installed supersu. Since miui already has a btter superuser manager, I decided to remove it. So I went to settings in supersu app and then chose the option that removes supersu so that we can install some other superuser manager.
Now I removed supersu, but it seems like miui su app is no more in use. Even though I have enabled root in that app, apps still say no root.
Please tell me how to fix this and get back to default miui su manager.
have you tried re-rooting via the app?, its in the android market,there are usually conflicts if you have two root apps, disable/ remove one and clear the data and start from scratch.
or just restore to the backup you made before you installed ubuntu,
Greetings Folks!!!
I am on CM12.1 Lollipop 5.1.1 Nightly, and ROOT access was working fine on my phone so far. When I launched Thunderzap today, I noticed that the app was waiting on "Requesting ROOT Privileges" for over 2 mins, and also the SuperSU app was missing from the app drawer. Thunderzap had been recently updated, and I suspect that might have triggered the root access to be requested again, but it wasn't given root access for some reason, and I never got a prompt to grant it root access. However, my other apps like ROOT Explorer, Shell Terminal Emulator etc, which weren't updated off lately, worked fine with root access. Not sure why now, but I thought reinstalling SuperSU-v2.46 might be a good idea at that time, and I flashed that file. And ever since I have completely lost my root access. When I launch the SuperSU app now, i get an error saying:- "There is no SU binary installed, and SuperSU cannot install it"
Some help would be appreciated. Screenshots attached.
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
acemccloud1 said:
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
Click to expand...
Click to collapse
can you please share the method u used to flash back CM?
i am unable to re root
I rooted with newest kingroot i currently don't have access to a computer atm, it displays ads on lockscreen and lags ive tried everything to replace w supersu it doesnt delete it ive noticed the script tries to delete "com.kinguser" stuff i also noticed they changed the kingroot apk to "cafeuser.apk" inside a folder called cafeuser i dont want to just delete it because like i said i dont have access to computer i want to know if anyone knows a successful way to uninstall this new kingroot 4.9.6 and keep root status and perhaps use superuser or supersu without computer access safely thank you for your time
Be advised im using a metropcs LG K7
LG MS330 running 5.1.1
may help
When asking for help you need to provide additional information such as device info:
sdk
manufacturer
model
However I faced the same problem too!
If I understood you correctly...so first thing first.
1. install superSU first & use root to install it as a system app any root apps can do that)
2. before rebooting the phone....please install busybox utilities from an app called "Busybox" on google play
3. reboot the device
4. once successfully rebooted open SuperSU & grant it root from kingroot & try to get it to install its binary.
- if it cant, disable kingroot after you know superSU was granted root & then try again.
-if it doesnt work again...then uninstall kingroot & relaunch SuperSU & try to let it install its binary again.
I have the lgms330 with the same kingroot version, did yours also automatically convert it to a system applies? I've never seen it do that on my other phones. Also my PlayStore stopped working when the update showed up there. Lol only good thing is Google also stopped telling me it would hurt the system. I have the newest version downloaded but I'm terrified to install it until I get some opinions cuz I currently don't have a monitor for my computer in case I brick it.
How to download kingroot