In previous versions, when you need a temp unroot to access certain apps for example, you can go to xbin and cut "su" "daemonsu" to other folder, that will make the root function temporarily disabled.
In the new system-less method however, i can no longer find su and daemonsu in xbin, is there any way to temporarily disable root without reflashing anything? Or do i have to roll back to the previous version because it is simply not possible?
Thanks in advance.
hhwong said:
In previous versions, when you need a temp unroot to access certain apps for example, you can go to xbin and cut "su" "daemonsu" to other folder, that will make the root function temporarily disabled.
In the new system-less method however, i can no longer find su and daemonsu in xbin, is there any way to temporarily disable root without reflashing anything? Or do i have to roll back to the previous version because it is simply not possible?
Thanks in advance.
Click to expand...
Click to collapse
Came across this post because I am looking for the same answer - anything new here?
Related
Hi guys,
I rooted my phone yesterday. This all went very well, the icon in my programlist is there but now...
I tried to remove some preinstalled programs with (an older version of) Root Explorer. When I push the button ' remount as R/W' nothing happends. So now I still can't remove any program from my phone?
Who has got the solution?!
Thanks!
PeterFdeVries said:
Hi guys,
I rooted my phone yesterday. This all went very well, the icon in my programlist is there but now...
I tried to remove some preinstalled programs with (an older version of) Root Explorer. When I push the button ' remount as R/W' nothing happends. So now I still can't remove any program from my phone?
Who has got the solution?!
Thanks!
Click to expand...
Click to collapse
If you don't have a current licensed version of root explorer, it may not work.
You could try Titanium. I use that to both delete apps and freeze them. On stock ROM, I generally only freeze them so OTA updates will still come through.
Try this app, works for me
Root Uninstaller
I can remove every app I want with Titanium Backup
Enable USB Debug mode
you can also freeze apps via adb.
just do
adb shell
pm list packages
pm disable com.app.App
where com.app.app is the program you'd like to disable
So I updated my D4 last week to the new build number. I kept root using the RootKeeper app. It indeed stayed rooted after, as I can still see the Superuser app in my app drawer. However, none of the privileges don't seem to work. For example, drocap2 won't take pictures and when I open Titanium, it tells me it couldn't get root access. It says "this attempt was made using the '/system/bin/su' command."
I haven't modded a phone since the OG, and I'm a bit rusty. Could someone help me solve this problem? Thanks!
AMTrombley0924 said:
So I updated my D4 last week to the new build number. I kept root using the RootKeeper app. It indeed stayed rooted after, as I can still see the Superuser app in my app drawer. However, none of the privileges don't seem to work. For example, drocap2 won't take pictures and when I open Titanium, it tells me it couldn't get root access. It says "this attempt was made using the '/system/bin/su' command."
I haven't modded a phone since the OG, and I'm a bit rusty. Could someone help me solve this problem? Thanks!
Click to expand...
Click to collapse
Stupid question but after you updated did you restore root with the Root Keeper app?
Sent from my DROID4 using XDA
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
AMTrombley0924 said:
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
Click to expand...
Click to collapse
Glad it was something easy!
Sent from my DROID4 using XDA
AMTrombley0924 said:
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
Click to expand...
Click to collapse
I am having the same issue, I restored using the root keeper app however the device rooted and root permission granted check boxes never go green. When I click restore root the su.apk pops up say permission was granted.
When I try and run such via the terminal app it command not found. I did look in /system/bin and such is there but no dice
---------- Post added at 04:39 AM ---------- Previous post was at 04:29 AM ----------
jnc8651 said:
I am having the same issue, I restored using the root keeper app however the device rooted and root permission granted check boxes never go green. When I click restore root the su.apk pops up say permission was granted.
When I try and run such via the terminal app it command not found. I did look in /system/bin and such is there but no dice
Click to expand...
Click to collapse
Well it turns out a backup was dropped in /system and it was called su-backup. I was able to obtain root that way then I remounted system and copied it over to /system/bin
So, as it turns out, I did not think to backup my root with Rootkeeper, and now after the update, I still have Superuser but I'm unable to grant any apps superuser permissions. I got the Droid 4 utility .3 and tried to reroot. Unroot, then reroot, and basically everything I could think of, and still, no luck.
PS - Isn't unrooting supposed to remove superuser? It did not.
I had the same problem. Basically what has happened is you have lost root access, but the apps that use root are still there, and without root access, the unroot function is unable to remove them.
What I did, was manually push the files using adb :
adb push motofail /data/local/motofail
adb shell chmod 755 /data/local/motofail
Then I tried the running the exploit to get root:
adb shell "/data/local/motofail exploit"
but it failed... I also tried remounting the system folder as rw and it failed so I couldn't get root.
After this, I booted into fastboot/recovery and wiped my data/cache. Then, I tried the rooting process again, got read/write permission errors (did not originally), wiped data/cache again, and finally tried the unroot process.
This got rid of my superuser.apk and su binary somehow.
After all of this, the rooting utility worked. So, once you manage to get rid of those files, you should be good to go. I apologize I cannot narrow it down any better.
Well, I appreciate your response, but I'm still not having any luck.
Here is what I did:
Rooted phone few weeks back, left it alone.
Installed update
Did a factory reset, superuser still intact, but not granting permissions
Came to these forums
Booted into recovery and wiped (Holding volume buttons at boot, pressing down then up, formatting cache and data/factory reset)
Tried to root using Droid 4 Utility .3 - Did not get many errors
Waited for that process, then again, booted into recovery and wiped
Ran Droid 4 Utility .3 UNROOT option.
Recieved errors in removing superuser.apk due to read-only file system. Permission was denied to remove the app data, system/bin, etc....
Please, I know there's a lot of topics/posts around here and other sites, but I feel like I've tried everything to the best of my knowledge and refuse to give up!
I had a similar problem. I had tinkered with my framework and the update would not install. Got that fixed but forgot to unroot before running the update and got stuck just like you. Tried several things but could not get root back nor completely unroot. In a fit of frustration i tried pete's roottools that i had used for my d2g and it uninstalled the superuser and then i was able to root with the d4 utility. The phone works fine but i suppose it could have upset some other part. So try at your own risk.
can you give me some details about your uninstalled the superuser ?i use the peter's roottool and can't find how to do it...
jsnweitzel said:
I had a similar problem. I had tinkered with my framework and the update would not install. Got that fixed but forgot to unroot before running the update and got stuck just like you. Tried several things but could not get root back nor completely unroot. In a fit of frustration i tried pete's roottools that i had used for my d2g and it uninstalled the superuser and then i was able to root with the d4 utility. The phone works fine but i suppose it could have upset some other part. So try at your own risk.
Click to expand...
Click to collapse
Hello there,
I have a sim-free htc one with with the original HTC rom. I rooted the phone (CWM and superSU) and confirmed successful root access with root checker.
I installed titanium backup because I wanted to get rid of the following applications.
7Digital
Facebook
Tweeter
Stocks
Deals
Kids mode
I successfully uninstall these apps with titanium backup. However if I power off or reboot the phone these applications re-install themselves.
Why is that happening?
Thanks,
Andrew
johnvfc said:
Hello there,
I have a sim-free htc one with with the original HTC rom. I rooted the phone (CWM and superSU) and confirmed successful root access with root checker.
I installed titanium backup because I wanted to get rid of the following applications.
7Digital
Facebook
Tweeter
Stocks
Deals
Kids mode
I successfully uninstall these apps with titanium backup. However if I power off or reboot the phone these applications re-install themselves.
Why is that happening?
Thanks,
Andrew
Click to expand...
Click to collapse
I've seen people mention this before and for some reason I seem to think it has something to do with the read/write ability of partitions? I'm probably completely wrong lol but anyways, have you tried deleting them or renaming them with a .bak at the end, using something like Root Explorer?
AllAboutTheCore said:
I've seen people mention this before and for some reason I seem to think it has something to do with the read/write ability of partitions? I'm probably completely wrong lol but anyways, have you tried deleting them or renaming them with a .bak at the end, using something like Root Explorer?
Click to expand...
Click to collapse
Hello,
Thanks for the reply. No I haven't try renaming them or deleting them.
How do I do that? I am using root browser app.
In which folder are these applications installed?
Thanks
Andrew
Hi,
If I'm not wrong you need a custom kernel with write protection disabled, you'll find them in the devellopment sections... It depends on the Android version you have actually, for 4.1.2 there is a totally stock kernel with write protection disabled, if you are on 4.2.2, try Bulletproof kernel close (or the closest) to stock.
Or take a look here: [KERNEL MODULE]Disable system write protection on stock kernel.
viking37 said:
Hi,
If I'm not wrong you need a custom kernel with write protection disabled, you'll find them in the devellopment sections... It depends on the Android version you have actually, for 4.1.2 there is a totally stock kernel with write protection disabled, if you are on 4.2.2, try Bulletproof kernel close (or the closest) to stock.
Or take a look here: [KERNEL MODULE]Disable system write protection on stock kernel.
Click to expand...
Click to collapse
If that's true then your better off using the stock Kernel from ARHD because that's 4.2.2 and you can 100% delete and rename system apk's ... Personally I'm not a huge fan of custom Kernels.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
johnvfc said:
Hello,
Thanks for the reply. No I haven't try renaming them or deleting them.
How do I do that? I am using root browser app.
In which folder are these applications installed?
Thanks
Andrew
Click to expand...
Click to collapse
Download an app like Root Explorer and navigate to "system/app" ... All the system apps are listed here. You can rename them so that they won't run after a reboot but there still there incase you want to revert back, or you can delete them. In Root Explorer you just have to long press on the apk and a list of options will pop up, 2 of which are rename and delete.
AllAboutTheCore said:
If that's true then your better off using the stock Kernel from ARHD because that's 4.2.2 and you can 100% delete and rename system apk's ... Personally I'm not a huge fan of custom Kernels.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
Download an app like Root Explorer and navigate to "system/app" ... All the system apps are listed here. You can rename them so that they won't run after a reboot but there still there incase you want to revert back, or you can delete them. In Root Explorer you just have to long press on the apk and a list of options will pop up, 2 of which are rename and delete.
Click to expand...
Click to collapse
Hello guys,
Thanks for the help, I will try first to rename the apps and if that does not work I will try to disable system write protection on stock kernel.
I will post the results.
Thanks,
Andrew
viking37 said:
Hi,
If I'm not wrong you need a custom kernel with write protection disabled, you'll find them in the devellopment sections... It depends on the Android version you have actually, for 4.1.2 there is a totally stock kernel with write protection disabled, if you are on 4.2.2, try Bulletproof kernel close (or the closest) to stock.
Or take a look here: [KERNEL MODULE]Disable system write protection on stock kernel.
Click to expand...
Click to collapse
viking37 thank you very much for pointing me to the right direction. I used this app https://play.google.com/store/apps/details?id=me.timos.htconerw and worked like a charm.
Andrew
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.
I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.
How can I overwrite the apk in the system?
tobos said:
How can I overwrite the apk in the system?
Click to expand...
Click to collapse
You will need root and unlocked bootloader.
kamalaggi said:
You will need root and unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
It is already rooted with bootloader unlock and magisk.
Can I do so afterwards?
tobos said:
Thanks for the reply.
It is already rooted with bootloader unlock and magisk.
Can I do so afterwards?
Click to expand...
Click to collapse
Yep. Either Uninstall using titanium backup or remove apk from wherever the system apk is. Then push (or copy) to destination and set permissions to 755
I can't overwrite it.
iArvee said:
Yep. Either Uninstall using titanium backup or remove apk from wherever the system apk is. Then push (or copy) to destination and set permissions to 755
Click to expand...
Click to collapse
Thanks for the reply.
The titanium backup allows me to disable the app, but not to delete it.
It also says Root Explorerde permissions change failed.
Is there any other way to do this?
tobos said:
Thanks for the reply.
The titanium backup allows me to disable the app, but not to delete it.
It also says Root Explorerde permissions change failed.
Is there any other way to do this?
Click to expand...
Click to collapse
FWIW I'm having the same issue. Titanium Backup Pro says it can't find the APKs and Remove System Apps app thinks it does and then really does nothing. I even tried Lucky Patcher, which does the same thing.
Root File Browser shows everything in System/App and System/Priv-App as being 755, but if I try to change it to 777, it says it fails. If I try to delete anything, it looks like it does it, but then nothing changes.
If I try to change permissions through ADB, it tells me that the file system is Read-only, and if I tried to run ADB as root, it tells me it cannot run as root in production builds.
Edit:
Solution: Install any terminal emulator, and the Debloater module from Magisk to remove system apps systemlessly (see Debloater module official thread here)
Edit 2: There are three apps, Call of Duty, Tidal 3 month free trial, and Linked in, which are located in /oem/app and they cannot be removed by this method. I do not know how to remove them...