I was using root fine before, but now it bugged up, so i checked around the device folders in TWRP and noticed /su was missing completely. I booted back into System and checked the folders, and su was there, with it's permissions at rwr-x--- (750) I'm pretty sure this is a bad situation. So how do I fix it back to 755??
SOLVED!! In TWRP i adb push the su binary to /system/bin & xbin, and it gave root to me again so i changed the permissions back to normal.
It also turns out my friend did this just to mess with me, but didn't think it'd end up like this...
Related
Device: Motorola Droid
ROM: CyanogenMod 6.1.2
Let me know if you need any other info other than this.
1. Cannot update su binary without flashing it from CWM recovery. I am currently up to date with 3.0.3 binary and 3.0.6 apk. See #2 for possible explanation.
2. Everything that calls for root access works except for, what I've noticed, apps that need /system/ and/or its subdirectories to be mounted as rw. *Superuser grants them the privileges, but the apps swear up and down that that isn't the case. Examples: ROM Toolbox, root file managers, etc. *Also, I cannot update busybox. It actually accepts the su privileges, but then fails. I can, however, install it to /mnt/sdcard/, not that that helps me. *There is also an app that has the option of mounting /system/ as rw, and while it says it works, I can't write to the directory or any of its subdirectories from any program. *I have Terminal Emulator, but I don't know enough about it to know what to do if that could help. I've gotten su privileges for it, but it won't let me access /system/. (side note: is there a way to flash busybox from CWM recovery and replace the WLAN files that I need to replace in /system/xbin/ and/or /system/bin/? In other words, since this worked for the su binary, would it work for those? If so, do u know of existing zip files or how I would go about making one?)
3. My wifi connects, tries to establish an ip address, and then is marked disabled and doesn't connect. I currently have it inactive. This has been happening since shortly after installing the CyanogenMod 6.1.2 -- not directly afterwards, but likely after installing and updating all my apps (I didn't install or update any system apps, as I knew not to).
Please let me know if you need to know anything else. I have searched and searched and searched for the answers to this problem, but I can't find it. In a nutshell I can't write to /system unless in recovery, and I can't use wifi at all. I did find some WLAN, etc files to replace the ones in /system with (a supposed wifi fix), but I obviously can't so that without write permissions.
Thank you so much in advance! I've figured out all my other previous issues on my own, but this one is a doozy!
Best,
SNJ
Me too - no mounting rw, busybox pro fails
Hi, I have the same problem on a Galaxy S with CM7.1. It just happened after I updated the last version of busybox pro. My wifi can't connect, everything which needs to mount system as rw fails, root explorer can't even start, and so the installation of busybox pro as well. It shows a huge list of apps which I need to symlink (never asked that before), and after trying installation it says that it appears as a different version of busybox than the one I selected was installed. I wonder if removing all the symlinked apps could do some good instead of leaving the overwrite option checked.
Anyone can help?
thanks
---------- Post added at 12:57 PM ---------- Previous post was at 12:24 PM ----------
just a small add-on. I tried a different busybox installer, and even if superuser indicated root access was granted, the app shut down telling it didn't detect root access.
???
OK, not really....I decided to do a system restore....bang, now I can only boot in recovery mode, not even the previous version but v.3.0.0.5, and I can't mount a thing, I get messages as unknown volume for path, unable process volume!....Now, how can I in any way wipe all and try to reinstall CM 7.1? phone doesn't get in download mode either.
Try flashing and moving files through adb.
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
I've installed tweaked 2.2 and it appears that I keep losing root. I re-flashed su and done the ADBRootfix listed in the tweaked thread.
Every time i open up terminal, i don't have root access and can only get a root shell. Running the ADBRootfix also gives me a root shell.
Searching has yielded me nothing and i've been stuck in adb trying to solve this.
Any ideas before I re-flash the whole rom?
Maybe clear the app data for Superuser, then go back into into terminal and su and see if you are prompted for superuser access. When you say root shell, are you referring to the $ prompt or the # prompt? Also, I assume other root apps no longer have root privileges, right? In the superuser app, what version of the su binary does it say you have installed?
I'm on su 3.1.3. by root shell i mean temporary roots that are gone every time i reboot. I go into terminal, su to get a # command line.
I can get apps to have root access such as tethering or screen shot apps, but it looks like I can't get the system rooted. I can't do things like uninstall apps that came with Tweaked.
I cleared out su data with no luck. I checked for updates in the SU app. It seemed like it kept thinking I had a legacy version. i reflashed the binary in cwm (per some SU discussions i read) and now i can't get SU to work. It's stuck trying to download the new binary via the SU app.
I think it's just time for a reflash from EP4. I feel like I'm missing something...I know my way around computers and I've been romming my phone for over a year...but regarding this problem, nothing seems to be making sense.
I think I just won't update SU from the play store on this round and see what happens.
sectiontape3137 said:
I'm on su 3.1.3. by root shell i mean temporary roots that are gone every time i reboot. I go into terminal, su to get a # command line.
I can get apps to have root access such as tethering or screen shot apps, but it looks like I can't get the system rooted. I can't do things like uninstall apps that came with Tweaked.
I cleared out su data with no luck. I checked for updates in the SU app. It seemed like it kept thinking I had a legacy version. i reflashed the binary in cwm (per some SU discussions i read) and now i can't get SU to work. It's stuck trying to download the new binary via the SU app.
I think it's just time for a reflash from EP4. I feel like I'm missing something...I know my way around computers and I've been romming my phone for over a year...but regarding this problem, nothing seems to be making sense.
I think I just won't update SU from the play store on this round and see what happens.
Click to expand...
Click to collapse
Had the same issue. Go into CWM and run Fix Permissions. This worked for me.
I ran fix permisions with no luck. More specifically, no luck with the losing root issue, I'll try it with the su binary update issue.
re flashed to EP4D, did the OTA. then flashed to tweaked. no root or su problems.
Hi All,
I have screwed up my android which was perfectly fine with a perfect root. Please help me to restore the root access !!!
Here is my problem description:
I have a Sony Xperia Miro which was perfectly rooted.
Model : ST23i
Android : 4.0.4 ICS
Build : 11.0.A.5.5
The root verification using app 'root checker basic' was successful.
Now I had few of my company apps and bank apps which wouldn't work in rooted device. But I never wished to lose my root status. So I was searching for the ways to hide root access from these apps. I even came across apps exclusively built for this purpose (hidemyroot/OTA root keeper) But due to some bad comments about these apps, I decided to try manually
The idea was to fool the apps when checking the root access.
At first I renamed the super user apps at the location /system/apps. to some invalid file(super.txt)
This did the trick for couple of apps which weren't working before in my mobile. However couple of apps were still failing.
The next thing I did was renaming .su to ku in the below location /system/bin/.ext
Then I verified Root Checker Status, still it displayed "u have root access"
Then I went to /system/xbin and renamed the following.
.su to ku
.busybox to busyboxk
.dexdump to dexdumpk
Then I tried Root Checker Basic again. And got the message "device don't have proper root"
But still my apps were not working. Then I did the most foolish thing which was restarting the device.
BAM.. !!!! I lost my root access permanently. Now I don't have superuser app. And I m not able to use 'Root explorer', to rename back the files to its original state.!!! And most ironic thing is my company app still saying I have root access. I tried after deleting its cache and data. The result was same !!
How can I restore my root access ? Please help
one update
Since I renamed the superuser and superSu applications, I couldn't use them.
Today I installed both of them using package installer.
But they doesn't seem to work as they can't find su binary installed
See the attached
appviz said:
See the attached
Click to expand...
Click to collapse
Do you have a Custom Recovery setup and if so did you make a backup after root?.
keifus.rahn said:
Do you have a Custom Recovery setup and if so did you make a backup after root?.
Click to expand...
Click to collapse
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
appviz said:
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
Click to expand...
Click to collapse
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your device. The same thing happend to me awhile back :/ If you want to save your apps use titanium back up or app backup & restore and add a custom recovery like cwmr so if this happens agen you wont have to reroot. if you are still having problems with your apps for work boot your phone into recovery and go to advanced then fix permisions if you have any other questions or any problems just let me know.
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
keifus.rahn said:
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
Click to expand...
Click to collapse
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
appviz said:
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
Click to expand...
Click to collapse
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
keifus.rahn said:
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
Click to expand...
Click to collapse
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
appviz said:
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
Click to expand...
Click to collapse
That's Awesome :highfive: I'm glad the hear that you got everything working correctly and with your company apps too. :victory:
Thank you for sharing with me and everyone. You never know if some one out there is having the same problem and this could really help them out one day.
I was trying to get rid of my "custom" status so I could take 4.4.2 OTA (I'm on 4.3). I had removed supersu and busybox and viper (the only things I had done with root anyway) and it wasn't going away. In hindsight, I think it was the build.prop changes for viper. In any case, I got the brilliant idea that the xbin directory itself, even though it was empty, was the issue and I deleted it. Now towelroot says it worked, but I'm thinking with no xbin directory it just silently fails. Obviously, without root, I can't put the xbin directory back.
Am I totally screwed or is there a way to fix this without wiping my phone?
So I ran the verizon upgrade assistant...
It pushed 4.4.2 to my phone.
Then it said the data partition was corrupt and needed to be reset to factory.
But instead I restarted the phone.
And it finished the upgrade. And the xbin directory is back. And, after initially still showing the status as custom, it now says "official".
And then towelroot didn't seem to work... So I installed supersu and it failed, but then after a reboot I had full root access again.
For the record, that left daemonsu, dexdump, su, sugote, sugote-mksh, and vril-dump in my xbin directory. Stock (right after the upgrade) had dexdump and vril-dump only in xbin.