A coworker of mine has an HTC ONE m7 on att and its oem unlocked, rooted, custom recovery installed. Everything else is stock. He recently wanted to unroot it and I tried to help, but everytime we removed the su binaries and apk they would just reappear.
I suspect this is because I was in a su shell to access these parts of the system, I thought a zip would be best so he wouldn't need me around to drop to shell and remount FS/etc.
I shamelessly took koush's original superuser.zip file and just modified the updater-script(he actually just uses updater-binary) and made it NOT copy all the new superuser stuff over, but left his code to clear out the existing superuser stuff.
I removed the extraneous files since I wasn't going to be copying them over as well.
Hope this is helpful
-J
Well I got access to an HTC ONE m7 on att this morning and this zip works fine. So if anyone was having issues actually removing superuser and the su binaries because they wanted to do something crazy like apply the stock OTA update, you can flash this, then flash your stock recovery back and you should be good to go assuming you're all stock.
Related
today i deodexed my /system/app/ and /system/framework/ successfully.
used root explorer to copy and paste the framework directory in place.
before i could do the same for the app directory - multiple errors resulting in a reboot to a bootloop
i have tried for a few hours now to create a update.zip with the odexed files to return to a working environment.. what i get on the screen is.. installing update.zip.. installation aborted... no errors or anything. (this is with the stock samsung recovery)
i do have a copy of the the original odexed files and the deodexed files.
clockwork recovery isnt supported for this phone yet so i can't go that route
i can't adb push the files because i need to grant adb superuser permissions from the phone.
so basically i have a nice fancy brick with a rotating droid animation on the screen.
the phone is a Samsung Gravity Smart SGH-T589
any suggestions?
btw - the firmware hasn't been released yet for this phone or i'd attempt a fix with odin.
Last I checked you may have to go a custom route to install a custom recovery. That step is always the weirdest, and it's never been the same for any of my phones. Especially if the phone isn't going to start up the conventional way...
Here are two places with more information that I found, maybe you didn't.
http://androidforums.com/samsung-gravity-smart/395877-yay-gravity-smart-forum.html
http://forum.xda-developers.com/showthread.php?p=17354030
hey thanks guy
i actually started both those threads a while back =)
i'm making progress with my update.zip
got it to install finally but still bootlooping
I'd like to try out ChainFire's SuperSU as I've heard good things about it...
I'm curious if I can just replace the SuperUser.apk in the root from recovery zip from Team Epic, put SuperSU.apk in its place and change the updater-script to install it, or if there is something else that I am totally missing..
Pretty new at all of this and want to make sure it'd work properly before I try it. :good:
no just install supersu
Install SuperSu, run it once, then delete the SuperUser.apk from /system/app. SuperSu will take over from there.
Thanks for the quick replies.
I'm trying to get ICS on my dad's phone, but for his company he needs it to be unrooted. The IT dept uses MobileIron which won't install unless the phone is unrooted. I flashed Shostock ROM and am trying to remove root. Now SU is gone, but I'm still able to access root directory using a file explorer. So it seems like the only way to fully unroot is to flash a stock ICS kernel. Where can I get one?
Or maybe someone has experience with MobileIron and can tell me if removing SuperUser is enough? Or does it also check for s-off?
You can extract the zImage from the UCLE5 plus Root tar package that is available in the development section.
You should however, leave the custom kernel on the phone and not install the stock UCLE5 kernel since that would introduce the risk of the eMMC superbrick bug.
Root does not reside within the kernel anyway. It is in the system partition, and since the phone is currently rooted, you can remove the files that make the phone rooted, and when you subsequently reboot the phone, it will no longer be rooted.
You will need to install a root file explorer. There are several available and I think at least one that is free on Google Play is a part of Super Manager 3.0 by Gpc. You can remove the applications after you remove root.
Be sure to remove all of the following before you reboot. You can't do it in steps. There is actually only one su binary and one busybox binary, but the other one of each of those is a symlink.
To remove root from the phone:
/system/app/superuser.apk
/system/bin/su
/system/bin/busybox
/system/xbin/su
/system/xbin/busybox
Thanks a lot. Those files are all gone, so I guess the phone is officially unrooted then. I was just worried since the root directory could still be accessed. I guess I won't be needing that official kernel then.
Thanks again!
mzaur said:
Thanks a lot. Those files are all gone, so I guess the phone is officially unrooted then. I was just worried since the root directory could still be accessed. I guess I won't be needing that official kernel then.
Thanks again!
Click to expand...
Click to collapse
You may be able to look at root in read-only but you won't be able to modify anything without root permissions.
Well, apparently the IT dept couldn't install MobileIron security software on the phone. I did remove all the root files, but I'm guessing it does check for unofficial kernels or something. I guess i'll have to give official ICS a try
mzaur said:
Well, apparently the IT dept couldn't install MobileIron security software on the phone. I did remove all the root files, but I'm guessing it does check for unofficial kernels or something. I guess i'll have to give official ICS a try
Click to expand...
Click to collapse
Not too surprised. You can find the UCLE5 stock firmware in the Download Repository.
Just don't do a wipe with that kernel installed !
Sent from my MB860 using Tapatalk 2
Hi guys, I'm new to XDA and I'm sorry if this is in the wrong section or if any thread already exists.
Alright, I own a Samsung Galaxy Tab 10.1v (GT-P7500) and yesterday I set my mind on rooting it. I checked several guides and saw that what almost everyone told was to use Odin3 to be able to use Clockwork mode and root it through flashing.
Well, I downloaded the zip and the recovery and everything seemed to be perfectly fine until, after flashing and booting the tablet I had no root access. Tried several apps for it (from a terminal to a root checker, and yeah, I know I didn't need to do it).
Anyway, after checking a bit I discovered that the su file nor the busybox didn't appear in the root folder (/system/bin o whatever his directory had to be) so I tried to flash it again. Nothing happened so I downloaded some other zips (the first one was like 2MB and the next one I tried was about 300KB), after this the su/busybox files appeared in its location, but when I tried to use the su command in the terminal I got the permission denied message. Used "ls -l /system/bin/su" to see that the permissions were this (if I recall correctly) ---sr-xr-x-.
After tearing my head apart after several hours of investigating and trying stuff I decided to do a factory reset so I could try (I hoped Superuser, su, busybox and all the other files would be erased) to root it again from scratch. Well, my surprise was the one you probably know, the /system files weren't reseted, I still had the Superuser app and all the other files, and su still had the same permissions and whats even more, it was 0KB though I don't know if the first time I tried to root it, it was already 0KB..
Well, this is my story, and if you could throw a bit of light on it I would be grateful.
Thanks in advance
P.S.: Sorry for my bad English
I have the Verizon Samsung Galaxy Note II running the stock MJ9 4.3 ROM. It's rooted (or at least was), but I haven't put on a custom recovery or done anything else.
I attempted to follow this post to replace my framework-res.apk using Root Explorer. Like some other people, I ran into trouble after rebooting, and now my phone hangs after the Verizon logo. I know that I need to use adb to restore framework-res.apk.
Except I can't get superuser permission to do so. First I saw that running su just hangs. Then I noticed that su wasn't setuid. So I used saferoot to put back a setuid su. It did make a new setuid su, but that su hangs, too. Also, after I reboot, the setuid permissions from setuid have been stripped. The saferoot method also put down a copy of su in /system/xbin/super, and that's retained setuid permissions, but that still hangs, too.
Is this because this is when a prompt would normally appear, but because my system isn't fully booted, it's just hanging?
Is there anyway around this? I could really use some help! I wasn't cautious enough to make sure I had a recent back before I started.
TIA.
I really dont know but I usually use odin to restore my phone to stock to start over fresh IMO
N3bula
Philz Recovery
Agni Control
I was able to restore my phone to normal functionality to compile getroot (from saferoot) from source, after adding a custom line to copy framework-res.apk back into place.
Major props to k1mu for saferoot, and for releasing the source code.