I rooted my phone and is verified with the root checker, but sometimes when I open up titanium it will say I don't have root privileges. I have to update super user and reboot in order for titanium to recognize it as rooted. I don't have to want to reboot it every time this happens. Is there a way around this? I've updated superuser almost everyday now.
What about uninstalling and then reinstalling tb???
Sent from my HTC One using xda app-developers app
If you are using a stock secure boot image but rooted you don't have full r/w access to the system drive. What I have found that works is opening Root explorer after a fresh boot, Mount the partition as r/w and then update superuser through the app, not the recovery method..
It should work fine after that
Sent from my Nexus 10 using Tapatalk HD
thanks!
Thanks! I got it updated and working.
altimax98 said:
If you are using a stock secure boot image but rooted you don't have full r/w access to the system drive. What I have found that works is opening Root explorer after a fresh boot, Mount the partition as r/w and then update superuser through the app, not the recovery method..
It should work fine after that
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Related
Hi guys,
i've rooted my girlfriend's Galaxy Ace with the universal v25.zip system.
Now if i run Root Checker it seems to be rooted perfectly, i got all green signs. But when for example i run some Root Needing apps such as System App Remover it says that System is not mounted. On my Optimus Black i can see this software says:
Root: Found
System: Mounted
Busybox: Found (Enabled)
on my GF's Ace it says
Root: Found
System: Not Mounted
Busybox: Found (Enabled)
how to solve this? This thing seems to cause problems to other root needing software like Gemini App Manager, when i try to block the autorun of some apps it hangs... it seems to be related to the same System Not Mounted.
Oh i forgot, another problem that i get is that when i open SuperSU it tries to update the binaries but then it says it's impossible to update...
thank you in advance for your help
[[[[ maybe wrong part of the forum to ask, if so, i ask moderator to close-delete the thread. thank you and sorry for this ]]]]
Root the ace again
Sent from my GT-S5830 using xda app-developers app
same method? or should i try a different root zip? (like that upd1.zip method)?
angelox82 said:
same method? or should i try a different root zip? (like that upd1.zip method)?
Click to expand...
Click to collapse
Try any
Sent from my GT-S5830 using xda app-developers app
at last i did it... dunno why but the V25 method didn't work, whatever i do (it's on stock 2.3.6 rom), so unrooted and then used the upd_1.zip method and now with superuser (the other puts superSU) i got full root and that app i tried to test says the system is mounted.
thank you for the support jumper
After updating my dream to cyanogenmod 5.0.8 ds, I realized a few problems. I have reflashed a few times, and a major gripe I have is that I can't seem to update the su binary to the latest version, it keeps failing at "gaining root access". I have also had to use the superuser update fixer to install the latest superuser version. The reason I want to install it is so that the stericson busybox installer will work, and thus metamorph will work, as it relies on the user having a semi-recent version of busybox.
P.S. I currently want to stick to cm5, as it is otherwise stable and full features. Any suggestions for another rom had better be convincing and involve a minimum of flashing.
I have the danger spl and cyanogen+jf recovery
Not sure if it's exactly what you need, but have a look here: http://forum.xda-developers.com/showthread.php?t=682828 I've noticed someone was talking about the Dream as well...
just try and uninstall super user all together and download superuser or super su from market, then try to update busbox through market app
I was able to get the su binary to update, but I'm not sure how. However, superuser is now denying everything, even freshly installed apps. What is going on?
Magicnet2 said:
Not sure if it's exactly what you need, but have a look here: http://forum.xda-developers.com/showthread.php?t=682828 I've noticed someone was talking about the Dream as well...
Click to expand...
Click to collapse
That is from a really early version of superuser, and it doesn't seem to fully answer my question, sorry.
can you uninstall current superuser and reinstall latest from market?
That is what I've already done. I couldn't update the su binary without doing so. All that cm5 seemed to have was the "superuser permissions" app.
When you go into the app do you have permissions denied? If your in an adb shell does it allow you su?
Sent from my Nexus 4 using XDA Premium 4 mobile app
When I go into any root app, superuser gives me a toast that says { } has been denied superuser permissions. The superuser app itself seems to have root access, though.
Try to just do it again, there's no reason I can think of this will happen
Just uninstall and reinstall su app, maybe try supersu, then use a busybox app to update. If this doesn't work again than try to manually do it
Sent from my Nexus 4 using XDA Premium 4 mobile app
Now, every time I try to do it, even after freshly flashing cm5, my phone does a boot loop.
Maybe try to extract contents of ROM and swap with new superuser
Sent from my Nexus 4 using XDA Premium 4 mobile app
At this point, I'm probably just going to try to get cm6 going on this thing.
Sure, check your other thread, I'll upload tonight
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks!
Hi,
Tried Everything, But neither ADB works nor root. Only flashing can write to system.
Used all sorts of techniques to mount /system as rw, but failed.
Using latest Rooted stock ROM(4.4.4 - 14.4.A.0.108) on my z1. Xposed Framework is also installed (flashed obviously as the system mount was not working)
As I am not able to write to system, unable to install the modded Google play (MOD EDIT, MENTION OF WAREZ IS STRICTLY FORBIDDEN IN XDA)
The app Busybox Installer was also unable to install the busybox, so flashed the latest busybox.
Used all sort of commands to make system rw using adb but none worked. Neither any app to mount /system in Play store did.
Flash tool was also unable to edit permissions to rw.
Please Help!!
Thanking XDA users and developers in advance
Warm Regards
Niraj
What tool did you use to root your phone?
Perhaps you can try re-rooting using rootkitXperia tool.
pkhrlniraj said:
Hi,
Tried Everything, But neither ADB works nor root. Only flashing can write to system.
Used all sorts of techniques to mount /system as rw, but failed.
Using latest Rooted stock ROM(4.4.4 - 14.4.A.0.108) on my z1. Xposed Framework is also installed (flashed obviously as the system mount was not working)
As I am not able to write to system, unable to install the modded Google play
The app Busybox Installer was also unable to install the busybox, so flashed the latest busybox.
Used all sort of commands to make system rw using adb but none worked. Neither any app to mount /system in Play store did.
Flash tool was also unable to edit permissions to rw.
Please Help!!
Thanking XDA users and developers in advance
Warm Regards
Niraj
Click to expand...
Click to collapse
Hi ,I had the very same problem a few weeks ago.
Solution... for me, was flashed stock 108 ftf and re-rooted using the latest version of Easy Root . I used V11.
Install SDFix: KitKat app from play store. And you should be good.
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, Sorry for mistake in post as I was a bit unaware about the same.
Also, I would request you to help me in in changing the value of Enable to 0 as it is showing 1 now.
Thanking you in advance.
Flash this https://www.dropbox.com/s/hvzh6ztcuur3vzw/disable_ric_file.zip
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Flash this https://www.dropbox.com/s/hvzh6ztcuur3vzw/disable_ric_file.zip
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the support.
Problem is solved, How can I close this thread?
gregbradley said:
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. Got my problem sorted out by changing 1 to 0.
Kjaups said:
Thank you. Got my problem sorted out by changing 1 to 0.
Click to expand...
Click to collapse
You will need to see if it sticks after a reboot though... if not you need to flash the disable-RIC zip
gregbradley said:
You will need to see if it sticks after a reboot though... if not you need to flash the disable-RIC zip
Click to expand...
Click to collapse
Somekind Disable_ric i already used and it ended with sdcard unreadable, so reverted and changed 1 to 0 and still rock solid
i was facing the same problem, a solution for it is to download an older version of busybox, the bb frm playstore(latest one) doesn't seems to work, i m using older bb pro....it sorted the issue..mounted rw /system...
hope it will help you.
using bb 9.2 pro though.
So I have a problem here. I rooted my X1049 with kingroot, to get temp root, removed write protection with the remount command on the terminal emulator, and installed Safestrap. It installed just fine. But when I reboot my phone to enter Safestrap, it doesn't show up, because when my phone boots up and I check the system partition with my file explorer, both Su and Safestrap have been removed. I have also tried to replace Kingroot with SuperSU, which doesn't work as when I open SuperSU it says I need to upgrade the Su binaries which fails. And when I reboot my phone, Su is removed, yet again. So to me it seems like the main problem is Android rolling back my changes to /system. I really need help with this, so plz respond as soon as possible.
Sent from my XT1049 using Tapatalk
Write protection cannot be turned off yet, all changes to /system will always rollback.
If anybody finds any way to disable write protection on the Moto X 4.4.4 please post here.
Sent from my XT1049 using Tapatalk
I know that some root methods have it so that when you enter recovery from the bootloader, android boots into write protection off. Does anyone know how this is done? And is it possible to do something like this on 4.4.4?
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Click to expand...
Click to collapse
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
optimumpro said:
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
Click to expand...
Click to collapse
I am using Kingo SuperUser to grant the apps root permission. Had some trouble replacing Kingo SuperUser with Chainfire SuperUser but I figured Kingo should've done the trick as well. When I mount Kingo did prompt me for permission and I allowed it, somehow I think the root is incomplete ?
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc.
...
...
somehow I think the root is incomplete ?
Click to expand...
Click to collapse
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
kentexcitebot said:
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
Click to expand...
Click to collapse
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Steven90 said:
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Click to expand...
Click to collapse
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
optimumpro said:
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
Click to expand...
Click to collapse
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Steven90 said:
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
Click to expand...
Click to collapse
Ulvgrim said:
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Click to expand...
Click to collapse
Try this, it's almost a one-click tool
http://forum.xda-developers.com/showthread.php?t=2784900
Exploit maybe works with 5.1.1, but if not, downgrade your firmware to 5.0.2, use Easyroot to exploit, then upgrade back.
The "classic" root I was referring to requires downgrading from Sony's Lollipop/Kitkat FW to Jellybean due to Sony patching the exploits in the newer FW used for rooting. The steps are outdated now and is replaced by Easyroot. http://forum.xda-developers.com/showthread.php?t=2688933