Hello community,
I was a reader of the site for long time. So I decided to register here, because I have some troubles with my new rooted Xperia Z.
Unfortunately all apps with root permissions are working a bit strange. Root Checker and Root Explorer are working after several crashes of Superuser. By opening these apps, I always get a message prompt, that Superuser has been terminated.
SuperSU doesn't work and quits while trying to install the in-app update.
I also changed the owner and the chmod permissions for these apps, but nothing changed at all.
It seems to me, that something went wrong during the root procedure. I completely followed the guide written by DooMLoRD(http://forum.xda-developers.com/showthread.php?t=2186368). The only different part was, that the service menu opened automatically. After that, I fixed the NFC issue. Hopefully, I don't have to reset the device.
Firmware build: 10.1.A.1.434
Do you have any suggestions for me?
Thanks a lot!
Fabowski said:
Hello community,
I was a reader of the site for long time. So I decided to register here, because I have some troubles with my new rooted Xperia Z.
Unfortunately all apps with root permissions are working a bit strange. Root Checker and Root Explorer are working after several crashes of Superuser. By opening these apps, I always get a message prompt, that Superuser has been terminated.
SuperSU doesn't work and quits while trying to install the in-app update.
I also changed the owner and the chmod permissions for these apps, but nothing changed at all.
It seems to me, that something went wrong during the root procedure. I completely followed the guide written by DooMLoRD(http://forum.xda-developers.com/showthread.php?t=2186368). The only different part was, that the service menu opened automatically. After that, I fixed the NFC issue. Hopefully, I don't have to reset the device.
Firmware build: 10.1.A.1.434
Do you have any suggestions for me?
Thanks a lot!
Click to expand...
Click to collapse
Try re-rooting the device
I already did a second try. Nothing changed, I've only got the message, that superuser app has been already installed.
Or do you mean, I have to reset the device and re-reoot it?
Any more suggestions here?
Sorry guys, I'm not a fan of bumping this topic, but before I try it with a factory reset, does anybody has a suggestion on this problem?
Related
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
furlessxp said:
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
Click to expand...
Click to collapse
Have you tried updating the superuser app itself? not only the su binary
Hello guys,
Yesterday I OTA-updated my xperia sp. Before the updating I made sure Voodoo Rootkeeper was installed and had a backup. After the updating root was still present, so I didn't have to use it. But, I tried to restore my old build.prop from .211 but after that phone crashed and rebooted. Same when installing xposed framework and trying to enable it. Also it won't let ES File-explorer mount /system R/W and won't let me uninstall the SuperSU app (crashed and reboots). Can anyone help me with this?
Kinda looks like I have to reroot my phone, but it's running fine (except for what I mentioned) and even offline charging works.
I'm pretty sure root access in this phone is not meant to be kept across versions. Besides, .2.254 uses a different way to root the phone compared to .211.
Catching my breath, letting it go, turning my cheek for the sake of the show
Solved
I already solved it, RIC wasn´t stopped at boot anymore. Thanks anyway
Hello. I found a Polaris office 5 link which will work with rooted devices http://forum.xda-developers.com/showthread.php?t=2611723. Installed as a systems app. I'm rooted, locked BL. After flashing in TWRP it will be there. Trying to open it gives the unfortunately app has stopped message. Looking to clear data in apps it shows no data at all. I go to root explorer find the apk, run in, install new and whamo - works great, no watermark, nothing. However, this is where the problem is, once I restart phone it is back to being uninstalled. It's still in system apps and libs are still there, permission are set. I'm not sure if I missed something. Followed the directions. Searched all over. Is this something to do with being rooted but still having a locked BL? If anyone knows the reason I know where the thank you button is.
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Disable OTA
Dmriskus said:
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Click to expand...
Click to collapse
1. Disable updates, link one post up
2. Root in TWRP
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Root Issue Reporting - "Could not access the package manager.Is the system running?"
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
kevinkoo said:
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
Click to expand...
Click to collapse
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
bkk99213 said:
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
Click to expand...
Click to collapse
Thanks man! I just resolved this issue, actually it's quite easy.. I just unchecked the option "Mount namespace seperation" in SuperSU, then everything works fine now!