I have successfully rooted my z1c,but I can't mount the system folder as rw. The reason why I want to do it is I have a problem with titanium backup which is unable to make a backup on external sd card. Of course I tried like 4 different methods to mount it by myself, including trying to remount it with es file manager, downloading different apps from google store, trying the script manager, but they still can't do it. Some write that an error occurred, some say that it's done although it's not. The only thing I didn't do yet is trying the adb, because I don't know how to use it. Can you please advise me how to solve this problem? Thank you in advance.
How did you root? There is a security feature which disallows mounting system as rw. It should be disabled if you rooted properly (with dualrecovery). If you don't have unlocked bootloader I'm afraid to tell you that you need to root again (from the beginning).
I rooted it using your guide
http://www.google.ca/url?sa=t&sourc...=MVoxMkzzStXsxO6UXWS_Aw&bvm=bv.67720277,d.cGU
I already rooted this way and made a backup of drm keys, but didn't unlock the bootloader yet.
In addition I updated the firmware using the link in your guide.
So do I simply unlock the bootloader? Or do I need to root it again?
And by the way I can't access any of the installed dual recoveries, neither the purple one nor cwm. The green led simply doesn't flash during the boot, is this okay? Did, and when, they disappear?
Sent from my D5503 using XDA Premium 4 mobile app
The link you posted is not my guide. Anyway it seems like you lost recovery. If you already have a TA backup you can proceed to unlock the bootloader. Then easily root by flashing a custom kernel + SuperSU.
zxz0O0 said:
The link you posted is not my guide. Anyway it seems like you lost recovery. If you already have a TA backup you can proceed to unlock the bootloader. Then easily root by flashing a custom kernel + SuperSU.
Click to expand...
Click to collapse
Sorry, i rooted it by this one: http://forum.xda-developers.com/showthread.php?t=2642081
When I unlock the bootloader, will the problem be solved?
necr0manser said:
Sorry, i rooted it by this one: http://forum.xda-developers.com/showthread.php?t=2642081
When I unlock the bootloader, will the problem be solved?
Click to expand...
Click to collapse
Probably already bootloader unlocking will solve your problem (mount system as rw), because I think the security feature gets deactivated. I still recommend to flash a custom kernel (I'm using the one by NUT) with recovery built in.
I know it's not directly related to this topic, but I am unable to open Android sdk although changing the Java_exe path. The cmd just flashes and closes immediately.
Sent from my D5503 using XDA Premium 4 mobile app
Thanks, I just unlocked the bootloader and patched the platform.xml file. It's solved now
necr0manser said:
Thanks, I just unlocked the bootloader and patched the platform.xml file. It's solved now
Click to expand...
Click to collapse
Not that it matters but platform.xml does not have anything to do with that problem (mount system as rw).
idk, but this stroke <group gid="media_rw" /> is what people say to add to this file in order to let apps write on external storage
Thank you
Related
Root. A word so simple, yet so complexed.
Every android user on XDA should know what it is, but people only know what they can do with it, not how and why.
There are already a ton of threads describing what root is, but here's something most of those threads forget:
To obtain root access, you need a 'su' binary inside /system/bin .
Also, you need an app to control apps that gain root privileges. The two you're most likely to hear about are SuperUser (SU) and SuperSuperUser (SuperSU).
So, if you have a recovery, you can flash a zip file that puts a su binary inside /system/bin , and installs the controller app (SuperUser and SuperSU). -- That way you don't need a PC to root your phone. Also, you don't lose any data and there's no risk of bricking your phone.
But, as I can see, people here aren't aware that they don't need PCs for rooting.
They flash kernels from all sorts of stock FW releases, use a billion programs, and finally, they get root after a good amount of time and flashing, usually with a lot of risk of bricks.
So, a quick step-by-step guide on how to do root like a pro:
1. You need a phone with a recovery and internet (be it WiFi or mobile data).
2. Go here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and save the file to your phone. Remember where you saved it!
3. Boot into recovery and flash the zip.
4. Reboot back into Android
Optional:
5. Realize that this process is far better than the ones that need a PC, because it's simpler. Thank me.
6. Tell it to your friends, so they don't mess around with huge downloads and flashing kernels.
someone755 said:
Root. A word so simple, yet so complexed.
Every android user on XDA should know what it is, but people only know what they can do with it, not how and why.
There are already a ton of threads describing what root is, but here's something most of those threads forget:
To obtain root access, you need a 'su' binary inside /system/bin .
Also, you need an app to control apps that gain root privileges. The two you're most likely to hear about are SuperUser (SU) and SuperSuperUser (SuperSU).
So, if you have a recovery, you can flash a zip file that puts a su binary inside /system/bin , and installs the controller app (SuperUser and SuperSU). -- That way you don't need a PC to root your phone. Also, you don't lose any data and there's no risk of bricking your phone.
But, as I can see, people here aren't aware that they don't need PCs for rooting.
They flash kernels from all sorts of stock FW releases, use a billion programs, and finally, they get root after a good amount of time and flashing, usually with a lot of risk of bricks.
So, a quick step-by-step guide on how to do root like a pro:
1. You need a phone with a recovery and internet (be it WiFi or mobile data).
2. Go here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and save the file to your phone. Remember where you saved it!
3. Boot into recovery and flash the zip.
4. Reboot back into Android
Optional:
5. Realize that this process is far better than the ones that need a PC, because it's simpler. Thank me.
6. Tell it to your friends, so they don't mess around with huge downloads and flashing kernels.
Click to expand...
Click to collapse
A Simple question, how can i get recovery, if for get it, i need first a root phone?
SteBanVe said:
A Simple question, how can i get recovery, if for get it, i need first a root phone?
Click to expand...
Click to collapse
I think u need an unlocked bootloader. U can root using bin4ry method without unlocking bootloader but it works upto 6.1.a.2.50 only.
Sent from my LT26i using xda app-developers app
bluechelsea said:
I think u need an unlocked bootloader. U can root using bin4ry method without unlocking bootloader but it works upto 6.1.a.2.50 only.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
i have Xperia S 2.55, and bin4ry method doest work. To apply this method, i repeat my question how can i get recovery, if for get it, i need first a rooted phone?
someone755 said:
1. You need a phone with a recovery...
Click to expand...
Click to collapse
How do you suppose we get a custom recovery without using different tools or unlocking bootloader?
Yes great guide, but only for UB ... for LB you need root BEFORE you install CWM...
al with .55 FW i recomend - flash any older rootable FW, root it, install CWM ... via CWM flash stockbased rom ( KA, XTX ) and thats all... or you an flash prerooted .55 FW ....
Okay, fine, schratch that!
Use goo.im manager from the play store and install the TWRP recovery!
Problem solved, but the main point is that people don't need PCs for root!!
someone755 said:
Okay, fine, schratch that!
Use goo.im manager from the play store and install the TWRP recovery!
Problem solved, but the main point is that people don't need PCs for root!!
Click to expand...
Click to collapse
I installed the app now how do i install recovery and boot into it?
Sent from my LT26i using xda app-developers app
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
I want to swap internal-external sdcard or mount folder app so that I can play big games with large data. For this, I rooted my phone with Impactor, and tried remount reboot fix by NUT and reboot fix by Anto Kus. But till now the phone reboots on using folder mount. Also my phone reboots while using a dual partitioned sdcard to use it with Link2sd. I have tested root checker which shows phone is rooted. I am using Titanium Backup without any problems. Should I go for bootloader unlock?
My phone xperia m dual c2004, 4.2.2, build 15.2.A.2.5.
Thanks
Sri007 said:
I want to swap internal-external sdcard or mount folder app so that I can play big games with large data. For this, I rooted my phone with Impactor, and tried remount reboot fix by NUT and reboot fix by Anto Kus. But till now the phone reboots on using folder mount. Also my phone reboots while using a dual partitioned sdcard to use it with Link2sd. I have tested root checker which shows phone is rooted. I am using Titanium Backup without any problems. Should I go for bootloader unlock?
My phone xperia m dual c2004, 4.2.2, build 15.2.A.2.5.
Thanks
Click to expand...
Click to collapse
Follow this guide step by step and dont forget to install busybox read carefully this guide
to play games i suggest you to install folder mount its better than swapping gl to sd n all
http://forum.xda-developers.com/showthread.php?t=2523597
Anmol0022 said:
Follow this guide step by step and dont forget to install busybox read carefully this guide
to play games i suggest you to install folder mount its better than swapping gl to sd n all
http://forum.xda-developers.com/showthread.php?t=2523597
Click to expand...
Click to collapse
I had already installed busybox and followed the procedure shown in the thread. The busybox is supported but inspite of root access, I can't change permissions in system files as a result the reboot fix is not working. Somewhere I read unlocking bootloader will help. Is it?
yes u must unlock bootloader for use full root access like change permission etc
mahithlal said:
yes u must unlock bootloader for use full root access like change permission etc
Click to expand...
Click to collapse
No, you don't need to unlock your bootloader to get full root access. Try this updated version of the reboot fix and then you're fully rooted...
Unlocking your bootloader will give you full root access without using root tools, exploits, etc., but many proprietary Sony apps will not work anymore because your DRM keys will be wiped when you unlock the bootloader...
mahithlal said:
yes u must unlock bootloader for use full root access like change permission etc
Click to expand...
Click to collapse
I have already backed up bootloader using TA backup and got bootloader key from Sony website. But can I claim warranty, if I restore locked bootloader? Or warranty is void, not reversible.
Unlocking your bootloader will give you full root access without using root tools, exploits, etc., but many proprietary Sony apps will not work anymore because your DRM keys will be wiped when you unlock the bootloader...[/QUOTE]
Ya, I know about the cons of unlocking bootloader. Thats why I am still waiting for other ways. I have also tried the fix by NUT from the forum which u gave link but still not fully rooted as it is unable to write in system folder. But other root operations like removing bloatware is done without any problems. Thats strange. Busybox is installed by NUT which supports part of the fix but the other scripts did not work in system.
By the your xm dual c2004 was updated to build 15.2.A.2.5 or is it from out of box like mine?
What script is basically not working
Anmol0022 said:
What script is basically not working
Click to expand...
Click to collapse
The scripts in the fix tool like killswitch.sh, etc. which needs to run to avoid reboot while mounting.
Sri007 said:
The scripts in the fix tool like killswitch.sh, etc. which needs to run to avoid reboot while mounting.
Click to expand...
Click to collapse
Well have not tried that but after rooting using that guide was able to use folder mount
Anmol0022 said:
Well have not tried that but after rooting using that guide was able to use folder mount
Click to expand...
Click to collapse
Is your phone same model and build like mine? I think it is due to the build version.
Sri007 said:
Is your phone same model and build like mine? I think it is due to the build version.
Click to expand...
Click to collapse
yes its same build 15.2.A.2.5
Stock Rom
If not working then you may update it via sony update service and reset phone
then follow guide again to root
According to guide use the same busybox as mentioned open and install it
or try from beggining again
Here are steps
use injector
install super su from google play
open and use super su
and install it binaries
install busy box x as mentioned
then open it and install allow root access if asked
then use reboot fix by NUT
follow cmd guide
and allow adb when ask permission
then phone will reboot
Then its written wait to check fix
And then its done press continue
done
use folder mount have fun
then
My C2004 also have full root access with locked bootloader, just updated to 15.2.A.2.5 through Sony Update Service, used Cydia Impactor, installed SuperSU from Play Store and then ran the script I linked to you. After all I have full root access, can remount system without problems and my bootloader still locked...
Anmol0022 said:
yes its same build 15.2.A.2.5
Stock Rom
If not working then you may update it via sony update service and reset phone
then follow guide again to root
According to guide use the same busybox as mentioned open and install it
or try from beggining again
Here are steps
use injector
install super su from google play
open and use super su
and install it binaries
install busy box x as mentioned
then open it and install allow root access if asked
then use reboot fix by NUT
follow cmd guide
and allow adb when ask permission
then phone will reboot
Then its written wait to check fix
And then its done press continue
done
use folder mount have fun
then
Click to expand...
Click to collapse
I have again followed the procedure as you mentioned. Everything worked except the fix. While waiting to check the fix, the phone reboots again. I am attaching the snapshots of the terminal window from which you may know the problem.
Its seems that is problem of busy box Bcoz it should show something like this
Anmol0022 said:
Its seems that is problem of busy box Bcoz it should show something like this
Click to expand...
Click to collapse
Ya, I know I have seen in a tutorial video on youtube. So, what's the solution you think? Which version of Busybox are you using?
Sri007 said:
Ya, I know I have seen in a tutorial video on youtube. So, what's the solution you think?
Click to expand...
Click to collapse
Well after installing busy box you have to open the app then in app you have to click install something like that have you done it
Anmol0022 said:
Well after installing busy box you have to open the app then in app you have to click install something like that have you done it
Click to expand...
Click to collapse
Ya, I have installed in normal mode busybox version 1.21.0, but on using the fix, it was replaced with busybox version 1.20.2-jb which support nohup or something. Which version of Busybox have you installed?
Sri007 said:
Ya, I have installed in normal mode busybox version 1.21.0, but on using the fix, it was replaced with busybox version 1.20.2-jb which support nohup or something. Which version of Busybox have you installed?
Click to expand...
Click to collapse
The same as mentioned from google play
Busy Box X by Robert
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
Download it again
from above link install it open it install then try fix again
Anmol0022 said:
The same as mentioned from google play
Busy Box X by Robert
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
Download it again
from above link install it open it install then try fix again
Click to expand...
Click to collapse
I tried to download it but the play store says it is not available in your country. Can you send me the apk?
follow this link
http://forum.xda-developers.com/showpost.php?p=51612704&postcount=12
link for advanced stock kernel xperia zl
http://forum.xda-developers.com/showthread.php?t=2641695
Search will give all your answers
Sent from my C6502 using XDA Premium 4 mobile app
I Did. Bt didnt get.
First of all this is wrong thread for your question and if you will search by using search option in forums you will find something
Now if u have locked bootloader then use nuts method check development thread
And if you are willing to unlockbootloader then there is easy way
Sent from my C6502 using XDA Premium 4 mobile app
It says that the previous version must be rooted. Bt mine wasnt rooted.
I rooted my device by unlocking bootloader
So if u r ready then i can help u
Pm me
Sent from my C6502 using XDA Premium 4 mobile app
May be later. I dont wanna unlock bootloader now.
You need to go back to 4.2 and use NUTS method to flash to 4.3 with root
Unlocking bootloader makes us to lose DRM keys. But to backup ta partition, rooting is required. To root, bootloader unlocking is required. Wtf
Downgrade is only option mate
Sent from my C6502 using XDA Premium 4 mobile app
So hw can i backup my TA?
Simple steps:
1. Downgrade to 4.2.2 (67 firmware) by flashing the ftf file of your region. Search the ZL thread to find your ROM on 67 fw.
2. Root the 67 firmware by bin4ry's method or cubeundcube method.
3. Make a TA backup using DevShaft's method. This is important for relocking your bootloader.
4. Upgrade to 101 using PCC or SUS. You will lose root. Make a ftf file of the update files that has been downloaded to your computer using flashtool.
5. Unlock bootloader from Sony. You will lose DRM.
6. Flash a custom kernel by Doomlord or Gustavo RD78. This is a modified stock kernel with cwm recovery built-in.
7. Now download the latest 1.94 update super su.zip from chainfire's website. Store it in your ext micro SD card. Flash it to root your phone from the cwm recovery.
8. To get back to stock recovery, use the ftf file created at step 4 above. Flash only the kernel and fotakernel from the ftf file.
9. Now relock your bootloader by flashing the ta backup you made at step 3. Now your phone is rooted with locked bootloader on 101 firmware.
10. Enjoy!
I made a similar help thread for Sony Xperia Z here: http://forum.xda-developers.com/showthread.php?t=2656698.
Go though the thread except using the custom kernel in that thread. That kernel is Z specific. For the ZL use the advanced stock kernel by Doomlord or Gustavo RD78 in the dev section. Link for kernel for ZL is here:
http://forum.xda-developers.com/showthread.php?t=2599619
Sent from one of my/our device/s
Yeah. I'll try
Rooted now.
I'm sorry, but isn't flashing 4.2.2 version (ftf .67), then rooting with kingo, then upgrading to .101 via OTA a much easier procedure?
alex_herrero said:
I'm sorry, but isn't flashing 4.2.2 version (ftf .67), then rooting with kingo, then upgrading to .101 via OTA a much easier procedure?
Click to expand...
Click to collapse
Kingo steals your IMEI and phone information while it roots. Some malware package is dropped onto your phone ( a long alpha numeric gibberish folder name with a dot in the begining to hide it). The folder is copied onto your phone's external SD card as well as onto your internal memory.This folder contains a .nomedia file sized 80 bytes, which is funny 'coz all nomedia files are 0 byte files. The file has some code stored in it, which is very suspicious. Avoid Kingo, vroot and all such Chinese fly-by night closed-source root methods that require an internet connection to root your phone.
Also read the last post in this thread for more information.
http://forum.xda-developers.com/showthread.php?t=2491457
Cookie Ninja said:
Kingo steals your IMEI and phone information while it roots. Some malware package is dropped onto your phone ( a long alpha numeric gibberish folder name with a dot in the begining to hide it). The folder is copied onto your phone's external SD card as well as onto your internal memory.This folder contains a .nomedia file sized 80 bytes, which is funny 'coz all nomedia files are 0 byte files. The file has some code stored in it, which is very suspicious. Avoid Kingo, vroot and all such Chinese fly-by night closed-source root methods that require an internet connection to root your phone.
Also read the last post in this thread for more information.
http://forum.xda-developers.com/showthread.php?t=2491457
Click to expand...
Click to collapse
Ok, sounds enough arguments for at least try another method. By the time I was rooting my device (a couple of months ago), kingo was the only method I could get my unlocked bootloader phone to keep root after upgrading to latest firmware through OTA (it was .569 back then). If someone is willing to point me (while I look by myself) to the method you followed to get root on a .101 firmware with a locked bootloader (mine can't be unlocked, AFAIK) I'll be more than glad!
Thanks for your comments.
deleted
Unlock Bootloader: NO
Cookie Ninja said:
Simple steps:...
Click to expand...
Click to collapse
Thanks for your guide!
But, what if my device's bootloader is not unlockable? On its information says: NO (to unlock bootloader) =(
No root for me?
Will we get root for 4.4 anyway? Aren't our dear developers (like the good @DooMLoRD) interested in helping us anymore?
- L
Hello, I have unlocked my bootloader and tried to root by hotbooting into the Doomlord Kernel with 6.0.4.6 CWM Recovery and installing the zip for SuperSU / Koush Superuser (tried both and the result is the same for either).
The problem is that the SuperSU/Superuser app will work fine and seems to grant access to read files in areas you normally need root for to read (eg data/data), however, if I try to delete a system app (like Facebook) with any root File Explorer after mounting system R/W it will fail to delete. I also cannot install things like Busybox using stericsson's tool as it will just fail. Other root apps like System cleanup do not delete either.
I did not have this problem in the 4.3 build (though I used the Docomo method with locked bootloader here).
Any ideas? Something to do with the SELinux??
paul5425 said:
Hello, I have unlocked my bootloader and tried to root by hotbooting into the Doomlord Kernel with CWM Recovery and installing the zip for SuperSU / Koush Superuser (tried both and the result is the same for either).
Click to expand...
Click to collapse
You need to use the kernel, not hot boot it, reverting to the stock kernel is why you're having issues.
XperienceD said:
You need to use the kernel, not hot boot it, reverting to the stock kernel is why you're having issues.
Click to expand...
Click to collapse
Thanks! That did the trick. I assume this must be a Sony-specific thing requiring some specific kernel changes? Perhaps I am mistaken, but I thought I remembered being able to hotboot Nexus devices and just root by flashing the Superuser zip.
paul5425 said:
Thanks! That did the trick. I assume this must be a Sony-specific thing requiring some specific kernel changes?
Click to expand...
Click to collapse
It is yes.
XperienceD said:
You need to use the kernel, not hot boot it, reverting to the stock kernel is why you're having issues.
Click to expand...
Click to collapse
Actually, there IS a way to hot-boot into CWM recovery with a custom kernel and then obtain root on your stock firmware/kernel. The problem is caused by Sony's RIC security feature which denies access to writing the /system partition, meaning that you only get a partial root . Solution involves running a command at every boot : http://forum.xda-developers.com/showpost.php?p=53085489&postcount=225