Database Users

[Q] 'failed to mount system'

Hi,
Unlocked and rooted stock 4.2 JOP40C Nexus 10, all has gone well. Root was successful, and apps like Titanium Backup, DataSync, and so on that require root all work fine.
However, when trying to mount /system in ES File Explorer or FileManager I get a message saying 'failed to mount system'. I'm trying to install the AOSP Browser but it won't let me paste the apk, nor will it let me change permissions for the folder.
I've tried downloading a couple of apps that say they will mount /system, but although I don't get an error message, /system doesn't mount either.
I'm stumped. Root was successful, but for some reason this isn't working.
Incidentally, before I unlocked and rooted the tab wouldn't take the 4.2.1 update with stock recovery. I assumed once I'd rooted I'd be able to apply a new ROM with TWRP. Backups work fine, but I get a status 7 on trying to install a new ROM. Could this be related - i.e, is TWRP also having trouble mounting /system?
Any clues would be very helpful! I've never had this much trouble rooting a Nexus device - currently own GNex and N7, and no problem rooting those...
Thanks.

Are you sure you have root? Check SuperSU or Superuser is installed. I always use SuperSU. Open the app & make sure binaries have updated.
Sent from my Nexus 10 using Tapatalk 2

djd338 said:
Are you sure you have root? Check SuperSU or Superuser is installed. I always use SuperSU. Open the app & make sure binaries have updated.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
The phone was rooted before I installed the rom. I don't have any apps on the phone right now because in the installation instructions, it said to do a clean swipe if installing the rom for the first time. So right now I don't have any apps.

[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

Nexus rooting problem

Hi,
I rooted my wifi Nexus 7 using Wugfresh toolkit and everything worked fine. After that I installed SmoothRom 4.3, which again went without a glitch. However, at some point I have noticed that the root is gone. This may have happened when I flashed Trinity kernel, but I am not sure. The Superuser SU is still there and couple of programs still have root access (e.g. Nova launcher), but Titanium backup no longer has root access (and it worked before). I re-rooted this morning using Wugfresh and everything went to the completion. I have Superuser SU and Busybox icons, but Busybox would not install and Titanium backup would not work due to the absence of root access. Any thoughts of what can be done to fix this?

Did you flash with TWRP or CWM? I have heard that you have to re-name some of the file names so that you do not lose the root access. You may have to re-flash and start from scratch but I am not sure. Personally i used MSKIP's toolkit. His has basically a 1.2.3........... root and flash setup. It is very easy to follow, plus one of the steps states "Do you wish to re-name file names so as not to lose Root access on restart." or something pertaining to that, I forgot exactly what it says, but I know that it is there.
visia said:
Hi,
I rooted my wifi Nexus 7 using Wugfresh toolkit and everything worked fine. After that I installed SmoothRom 4.3, which again went without a glitch. However, at some point I have noticed that the root is gone. This may have happened when I flashed Trinity kernel, but I am not sure. The Superuser SU is still there and couple of programs still have root access (e.g. Nova launcher), but Titanium backup no longer has root access (and it worked before). I re-rooted this morning using Wugfresh and everything went to the completion. I have Superuser SU and Busybox icons, but Busybox would not install and Titanium backup would not work due to the absence of root access. Any thoughts of what can be done to fix this?
Click to expand...
Click to collapse

I had the same issue. If you reflash the ROM, the problem corrects temporarily. It may be something w/the most recent version of Smooth- particularly when updates are made to Super User. I tried several different kernels and still "lost" root. Eventually I moved on to another ROM and have not had the issue since.

Thanks for the suggestions. I am using CMW. Tried MSKIP toolbox, but same result. Titanium gave back an error message that device appears to be rooted, but Superuser SU is not working properly. So, I went back and did CMW restore from an earlier backup, which seems to have fixed the problem. Titanium is working again.

There is no SU binary installed, and SuperSU cannot install it

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