Now I know I'm rooted. I unlocked my bootloader, flashed CWM 3.0 and installed the Superuser (ef) and even installed Rom manager and gave it permission. But for some reason almost every other rooted app I download and try to use it says that my phone isn't rooted?? I'm using a Nexus S. Anybody had similiar issues and resolved it? Thanks for all responses.
Yes the answer has been posted. Go into the recovery from rom manager or by volume and power. Go to mounts and storage and mount / system. You are see it unmount now so mount the system.
You may also need to zap the system with chmod.
You do this by going into Clockwork Recovery's Mounts & Storage. Mount /system. Then in ADB from your computer type in:
1) adb shell
2) cd /system/bin
3) chmod 6775 su
exit and reboot.
Related
Does anyone know how to install this on the aria?
http://forum.xda-developers.com/showthread.php?t=682828
It's best to flash your Aria to a Liberated ROM. You can find it within the forums here. Since I can't post links yet. This will root the device and SuperUser will be added.
Not sure about that app. It looks like it does the same thing as the SU that comes in the Liberated ROM by attn1, just without the few extra options.
I tried booting into clockwork and mounting the system partition and doing this:
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot
but when it rebooted the superuser app did nothing at all. No prompt or nothing running apps that needs su. I had usb debugging enabled. So I just restored a nand backup.
Might be a dumb question, but did you do adb remount ?
I used clockwork to mount the system partition. When I tried it with just adb remount it wouldn't mount the system partition. I would always get "Not a directory" error. But when clockwork mounted the partition it wrote the files fine with no error. When I rebooted the superuser icon and version were different than the one that came with the liberated rom.
I'm trying this now, I'll report back when I do it. I'll try a few different apps that require SU
I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.
It's probably not compatible with our phone yet.
Could be, but I'm pretty sure it does work, because if I remember correctly, Titanium Backup needs SU permissions, and I haven't encountered any kind of errors with it yet.
I see you posted on the thread for the program itself. Hopefully someone there will have a response.
Yeah, I'm hoping to get a response to it. We will see.
The newer version 2.2.2 works.
Awesome, ill give it a shot a little later.
Tried the newer version, and I get the same issues.
How did you install this one? I booted in to clockwork and selected install from zip file on sd and selected that file on my sd card.
I just did it through adb. I'll give that method a shot.
Looks like after doing your method, it works perfect now. Not sure why using adb doesn't work.
So i rooted my vibrant with the hopes of removing some of the bloatware. i rooted with the one click root method, loaded clockwork recovery, i know i am rooted but every time i try adb remount i get remount failed: no such file or directory.
so i tried going into clockwork recovery in the partition menu and mounting system there and trying adb remount and got remount failed: operation not permited. i ran adb root and got root can not run on factory builds (or something close to that)
in adb shell ive tried mounting every which way i can think of and nothing works.
ive searched all over and havent been able to find a fix, please help
root explorer didnt work either
also i tried deleting the system apps with root explorer and it would mount either
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
cojonesx said:
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
Click to expand...
Click to collapse
like i said in my post, i tried shell and couldnt get it to mount. maybe i did it wrong
Hi I have been trying all evening to remove com.wsandroid.apk from my phone, using terminal but I simply cannot. I've tried many different commands and I'm just being told either permission denied, directory not found/not empty. I have a Wildfire which is obviously rooted. Please help me out, tearing my hair out here.
So you're using modaco custom rom?
Download the latest version of HTC Sync and install. This will also install the adb drivers. (I presume you use windows, if not, I apologise)
Download the Android SDK
Put the phone in fastboot mode (Power+Volume down) and plug it into your computer.
When the drivers are installed, use the command prompt to navigate to the tools folder within the android sdk folder.
Type the following commands, pressing enter at the end of each line:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
cd app
rm -r com.wsandroid.apk
That should do it
I'm using the stock ROM but it is rooted with Unrevoked. I'll try these instructions anyway.
- Connect your phone to the PC
- Clear WaveScure's cache on the phone
- Open a command prompt
- go to run go to C:\androidSDK\tools and then run these 2 commands
1. adb remount
2. adb shell rm /system/app/*wsandroid*
Click to expand...
Click to collapse
I'm trying these settings, but when I get to adb remount, I get this error: remount failed: Operation not permitted
EDIT: I put the phone into recovery mode and mounted it and it said remount succeeded, I then followed step 2. both *wsandroid* and com.wsandroid.apk and it says that they cannot be found.
EDIT: Nevermind, deleted it
There's currently no write access to system partition using Unrevoked on Wildfire. So you can't remove it. You flashed it with update.zip? I'm not an expert (yet) but I assume the only way (or easiest way) to remove it is to flash your stock ROM again.
Today I tried to enable ART on my S3 Mini running Maclaw's CM11. After the phone was shut down, the CM loading circle stayed there forever and the phone didn't boot.
To fix this you can boot the phone into recovery (I'm using CWM) and use ADB to revert the runtime back to Dalvik.
There are 3 ways to do this:
Use the following manual instructions
Download the second attachment and run the batch file, while the phone is connected using a USB cable and in recovery mode. For this you need USB drivers installed.
Download the first attachment and flash it in recovery
Manual instructions
Boot to recovery
Open the shell
Code:
adb shell
Now, while in the shell, the data filesystem must be mounted.
Code:
mount /data
Still staying in the shell, use the following command to set Dalvik as the runtime of choice.
Code:
setprop persist.sys.dalvik.vm.lib libdvm.so
Now the /data-filesystem can be unmounted using
Code:
umount /data
Type exit in the shell to exit ADB shell.
Reboot the phone and it should get past the loading circle again
If anything goes wrong, I'm not responsible
Very good idea. Thanks
I am not sure, but maybe it is possible to set property from recovery update script?
Such script, downloaded onto phone and accessible from recovery would be better, than PC with USB drivers and a cable
piskor said:
Very good idea. Thanks
I am not sure, but maybe it is possible to set property from recovery update script?
Such script, downloaded onto phone and accessible from recovery would be better, than PC with USB drivers and a cable
Click to expand...
Click to collapse
Thank you for the idea, implemented it now and added to the OP.
dextrey said:
Thank you for the idea, implemented it now and added to the OP.
Click to expand...
Click to collapse
Excellent, thanks
Updated to mount the /data filesystem directly using the fstab entry. Also changed the recovery-flashable .ZIP to use a temporary BusyBox for all commands, because I'm not completely sure about the filesystem differences between different ROMs and recoveries (the locations of binaries such as mount and umount)
Thanks!!!
Very useful!!
Thanks, this worked. I was on CM11 nightlies and read an article about ART and switched it from Dalvik, phone app crashed and wouldnt let me boot in. Although I'm using HTC One, this method worked for me.
For TWRP users, boot into recovery and go into Advanced, and then use terminal to command the type the main line to switch to Dalvik, no need to adb shell and mount data.
Fixed my HTC ONE m7 that got brinked when selecting ART.
dextrey said:
Today I tried to enable ART on my S3 Mini running Maclaw's CM11. After the phone was shut down, the CM loading circle stayed there forever and the phone didn't boot.
To fix this you can boot the phone into recovery (I'm using CWM) and use ADB to revert the runtime back to Dalvik.
There are 3 ways to do this:
Use the following manual instructions
Download the second attachment and run the batch file, while the phone is connected using a USB cable and in recovery mode. For this you need USB drivers installed.
Download the first attachment and flash it in recovery
Manual instructions
Boot to recovery
Open the shell
Code:
adb shell
Now, while in the shell, the data filesystem must be mounted.
Code:
mount /data
Still staying in the shell, use the following command to set Dalvik as the runtime of choice.
Code:
setprop persist.sys.dalvik.vm.lib libdvm.so
Now the /data-filesystem can be unmounted using
Code:
umount /data
Type exit in the shell to exit ADB shell.
Reboot the phone and it should get past the loading circle again
If anything goes wrong, I'm not responsible
Click to expand...
Click to collapse
Thank you, thank you, I'm in great debt for this.
Can recommend the method if you are running viperOne 6** on a HTC one m7 (bulletproof kernel).
NB:
My ADB was totally broken, but I wrote all commands in the TWRP terminal window, and it reverted my phone back to dalvic from ART!
I'm trying to delete the audio conf file in system/vendor/etc but it won't let me. I'm rooted and running Pure Nexus.
Also when I go into the recovery and try to use the file manager it doesn't show me any files in that folder even though there are files in there.
I just updated the Rom the other day. What could have gone wrong?
Sent from my Nexus 7 using Tapatalk
you need to mount the system partition as writable first. Issue from the dos command prompt:
adb root
adb remount
and then try again and it should work.
*EDIT* that's from within the normal system. You're also asking about recovery. In that case you need to mount /system first. Click on the 'mount' button inside TWRP and select system and vendor. Then you should be able to delete the file too (make sure you didnt select 'mount system partition read-only'). So that's a solution if you don't have adb installed.
gekkehenkie11 said:
you need to mount the system partition as writable first. Issue from the dos command prompt:
adb root
adb remount
and then try again and it should work.
*EDIT* that's from within the normal system. You're also asking about recovery. In that case you need to mount /system first. Click on the 'mount' button inside TWRP and select system and vendor. Then you should be able to delete the file too (make sure you didnt select 'mount system partition read-only'). So that's a solution if you don't have adb installed.
Click to expand...
Click to collapse
The worked when I did it in the recovery. Thanks so much
Sent from my Nexus 6P using Tapatalk