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
Related
So i Have been working on my new rom, now i Have it all AOSP as i can, and just have sense stuff we need, but now i have no root access, none of my root apps will work, i need help becuase i need root access to run a lot of helpful programs, i think i deleted someth ing in the sy stem folder that was important to root.
rtbluver said:
So i Have been working on my new rom, now i Have it all AOSP as i can, and just have sense stuff we need, but now i have no root access, none of my root apps will work, i need help becuase i need root access to run a lot of helpful programs, i think i deleted someth ing in the sy stem folder that was important to root.
Click to expand...
Click to collapse
my app root check, for free on the market, when run in advanced mode will give the technical details as to which files might be missing or configured incorrectly.
easiest solution is to download superuser.apk from the market or flash the superuser install .zip from recovery which should reconfigure the complete root setup.
hopefully that works, if not, let us know!
joeykrim said:
my app root check, for free on the market, when run in advanced mode will give the technical details as to which files might be missing or configured incorrectly.
easiest solution is to download superuser.apk from the market or flash the superuser install .zip from recovery which should reconfigure the complete root setup.
hopefully that works, if not, let us know!
Click to expand...
Click to collapse
Doin it all now, but it looks like i deleted something good, because my wifi is giving me errors too. So I mightve deleted some framework. Hmmm
rtbluver said:
Doin it all now, but it looks like i deleted something good, because my wifi is giving me errors too. So I mightve deleted some framework. Hmmm
Click to expand...
Click to collapse
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
Standard su binary location: ls -l /system/bin/su:
null
Standard su binary location: ls -l /system/xbin/su:
null
Alternate su binary location: ls -l /sbin/su:
null
SU binary not found or not operating properly
Results provided by Root Checker version 3.4 from joeykrim in the Android Market - http://goo.gl/GgWae
Root checker stats when i run the advanced check, I just flashed su zip too. Is there something in the framework for editing root, becuase wifi is error too, hmm more flashing and checking.
rtbluver said:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
Standard su binary location: ls -l /system/bin/su:
null
Standard su binary location: ls -l /system/xbin/su:
null
Alternate su binary location: ls -l /sbin/su:
null
SU binary not found or not operating properly
Results provided by Root Checker version 3.4 from joeykrim in the Android Market - http://goo.gl/GgWae
Root checker stats when i run the advanced check, I just flashed su zip too. Is there something in the framework for editing root, becuase wifi is error too, hmm more flashing and checking.
Click to expand...
Click to collapse
i've never seen null in the results ... and you say you have a wifi error.
i would suggest reflashing whatever ROM you're currently on. when you flash a ROM, they generally wipe your /system and reload a full /system.
if you're on a custom kernel, i'd also reflash the kernel (kernel .zip files will include its required modules) as the kernel and modules, including wifi, in /system/lib/modules have to match.
as long as you flash the same ROM you're currently running, you *shouldn't* have to wipe data.
i'm not sure what you might have erased but making a nandroid backup for you venture into modifying system files is generally a good practice!
edit: i see in your signature you're running your own ROM. assuming you have more knowledge/experience than average, if you'd prefer not to flash over your current ROM and lose whatever changes you've made that you do want to keep, you could try swapping individual files from the original ROM back onto your current system as see if that fixes the issues.
although for the wifi issue, since your signature shows silverneedle, i'd just flash silverneedle and that should guarantee the wifi modules match up with the kernel and clear the wifi issue. if the wifi issue isnt cleared, then something else in /system might have been modified and you're back to swapping individual files from the known working rom.
hope that helps!
joeykrim said:
i've never seen null in the results ... and you say you have a wifi error.
i would suggest reflashing whatever ROM you're currently on. when you flash a ROM, they generally wipe your /system and reload a full /system.
if you're on a custom kernel, i'd also reflash the kernel (kernel .zip files will include its required modules) as the kernel and modules, including wifi, in /system/lib/modules have to match.
as long as you flash the same ROM you're currently running, you *shouldn't* have to wipe data.
i'm not sure what you might have erased but making a nandroid backup for you venture into modifying system files is generally a good practice!
edit: i see in your signature you're running your own ROM. assuming you have more knowledge/experience than average, if you'd prefer not to flash over your current ROM and lose whatever changes you've made that you do want to keep, you could try swapping individual files from the original ROM back onto your current system as see if that fixes the issues.
although for the wifi issue, since your signature shows silverneedle, i'd just flash silverneedle and that should guarantee the wifi modules match up with the kernel and clear the wifi issue. if the wifi issue isnt cleared, then something else in /system might have been modified and you're back to swapping individual files from the known working rom.
hope that helps!
Click to expand...
Click to collapse
Yah, Im trying files out, updated busybox, but my wifi problem may lie in the kernel change with the ROM, because i changed my ROMs kernels to RCmix and now im getting the wifi error, but Im trying to go into the rom system, to see what i screwed up, i will report back.
rtbluver said:
Yah, Im trying files out, updated busybox, but my wifi problem may lie in the kernel change with the ROM, because i changed my ROMs kernels to RCmix and now im getting the wifi error, but Im trying to go into the rom system, to see what i screwed up, i will report back.
Click to expand...
Click to collapse
Placed Busybox in wrong directory! Im all good now, thanks!
Hey first time posting, prior to unlocking the bootloader on my Photon 4g I had a bunch of ROM's listed in ROM Manager. After I got it unlocked I only see four options, Font Packs for Android 4.0, Cerberus, Superuser, Google Apps, ClockworkMod. Also, I cannot back up through ROM Manager either, it results in a white triangle with a yellow exclamation point. I am currently running stock Android 2.3.4 no ROM running. It worked perfect before I unlocked my Photon, any advice?
You sure the roms you saw were for the photon? If I had to take a blind guess id go with when rom manager was initially installed the device wasn't rooted, and the app was unable to determine which device you had and was showing roms for all phones. Now that you're rooted and the app has permission and can read the device fingerprint and is able to display the proper downloads.
KSmithInNY said:
You sure the roms you saw were for the photon? If I had to take a blind guess id go with when rom manager was initially installed the device wasn't rooted, and the app was unable to determine which device you had and was showing roms for all phones. Now that you're rooted and the app has permission and can read the device fingerprint and is able to display the proper downloads.
Click to expand...
Click to collapse
That's kind of what I was thinking, my phone was rooted prior to the unlock when I was viewing the roms. But I don't know much about all this since this is my first unlock. I do know some phones do not have a list in ROM Manager. Any ideas as to the backup issue?
You need to delete a file off your phone that installs stock recovery every time it boots. You can adb or use and explorer that can modify /system like root explorer, and delete install-recovery.sh from /system/etc
Once deleted power down into fastboot and reflash CWM or do it through rom manager. Either way you need to delete that file because it's forcing you back to stock recovery.
Good luck
KSmithInNY said:
You need to delete a file off your phone that installs stock recovery every time it boots. You can adb or use and explorer that can modify /system like root explorer, and delete install-recovery.sh from /system/etc
Once deleted power down into fastboot and reflash CWM or do it through rom manager. Either way you need to delete that file because it's forcing you back to stock recovery.
Good luck
Click to expand...
Click to collapse
That would explain a lot. I'll give that a shot. Thank you!
KSmithInNY said:
You need to delete a file off your phone that installs stock recovery every time it boots. You can adb or use and explorer that can modify /system like root explorer, and delete install-recovery.sh from /system/etc
Once deleted power down into fastboot and reflash CWM or do it through rom manager. Either way you need to delete that file because it's forcing you back to stock recovery.
Good luck
Click to expand...
Click to collapse
That would explain a lot, I'll give that a shot. Thank you!
I am running stock DNA, rooted, and with CWM touch recovery. For myself, being root is not merely a luxury, it is a need. Most importantly, I cannot stand having a crippled unix terminal without busybox, which of course, requires root.
I know not what the imminent OTA will bring, but root is too precious to risk losing. I would therefore like to engage in a DNA-specifc discussion about disabling the OTA update.
From what I can tell so far, the two methods include:
1) renaming the otacerts.zip file in /etc/security to a .bak file. This will not work in the present case, since /etc is mounted at /system/etc, and /system can only temporarily be mounted rw due to us being stuck with "S-ON" for now.
2) installing "FOTAkill.apk", or, flashing its corresponding zip (attached below) in custom recovery. Again, in the present case, this file was written for the EVO, and will most certainly not work. The updater-script in the zip can be modified to reflect the correct mount points, but there is a corresponding binary which I have no clue contains what, and would certainly need some expert opinion about.
Any ideas ye fine fellers?
You could always do load ota root keeper from the market back your root up temp un root via app update ota and then re root using the app, I have done this on other devices and I never lost root. Worked well. Might be worth a shot.
Sent from my HTC6435LVW using xda app-developers app
manzdagratiano said:
I am running stock DNA, rooted, and with CWM touch recovery. For myself, being root is not merely a luxury, it is a need. Most importantly, I cannot stand having a crippled unix terminal without busybox, which of course, requires root.
I know not what the imminent OTA will bring, but root is too precious to risk losing. I would therefore like to engage in a DNA-specifc discussion about disabling the OTA update.
From what I can tell so far, the two methods include:
1) renaming the otacerts.zip file in /etc/security to a .bak file. This will not work in the present case, since /etc is mounted at /system/etc, and /system can only temporarily be mounted rw due to us being stuck with "S-ON" for now.
2) installing "FOTAkill.apk", or, flashing its corresponding zip (attached below) in custom recovery. Again, in the present case, this file was written for the EVO, and will most certainly not work. The updater-script in the zip can be modified to reflect the correct mount points, but there is a corresponding binary which I have no clue contains what, and would certainly need some expert opinion about.
Any ideas ye fine fellers?
Click to expand...
Click to collapse
There are system writable kernels out there, and you can always rename your files in recovery. S-Off is not an issue in this scenario.
delete checkinprovider.apk, cotaclient.apk, and updater.apk from /system/app
Jaggar345 said:
You could always do load ota root keeper from the market back your root up temp un root via app update ota and then re root using the app, I have done this on other devices and I never lost root. Worked well. Might be worth a shot.
Click to expand...
Click to collapse
I have indeed heard this alternative thrown around but I am not willing to chance it; I have seen an equal amount of horror stories about people having their systems fried with this method (the Droid X for instance, which I had and where the last update broke root).
SolusCado said:
There are system writable kernels out there, and you can always rename your files in recovery. S-Off is not an issue in this scenario.
Click to expand...
Click to collapse
I will look at what's out there and if it is stable enough to be flashed. How does one rename files in recovery though? I rebooted into CWM (touch) and I see no such option - unless you can remount a partition and rename files in it somehow.
nitsuj17 said:
delete checkinprovider.apk, cotaclient.apk, and updater.apk from /system/app
Click to expand...
Click to collapse
This avenue seems promising. Has anyone tried this before? Also, how does one delete these in the S-ON situation? (I'm assuming recovery is the answer). I feel if I remounted rw, deleted and then rebooted, they will be right back where they are.
manzdagratiano said:
This avenue seems promising. Has anyone tried this before? Also, how does one delete these in the S-ON situation? (I'm assuming recovery is the answer). I feel if I remounted rw, deleted and then rebooted, they will be right back where they are.
Click to expand...
Click to collapse
If you install a kernel with /system writing enabled you can just delete them normally.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you install a kernel with /system writing enabled you can just delete them normally.
Click to expand...
Click to collapse
Great... thanks! I am looking into custom kernels. By the way, if custom kernels that do allow write to /system can be concocted, why is S-ON an issue at all? I was under the impression that this has to do with NAND memory being inaccessible, which seems to be a lower level issue than the kernel.
manzdagratiano said:
Great... thanks! I am looking into custom kernels. By the way, if custom kernels that do allow write to /system can be concocted, why is S-ON an issue at all? I was under the impression that this has to do with NAND memory being inaccessible, which seems to be a lower level issue than the kernel.
Click to expand...
Click to collapse
With s on we can not.
Flash radios
Flash kernels in recovery.
Change the splash screen
Go back to a locked bootloader
And a few other things I'm probably forgetting.
Sent from my HTC6435LVW using xda app-developers app
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.
Hi everybody. I learned so much from this forum (and also from others) in one year and tried to share my knowledge to those who try to learn like me.
Now i would like to share one of my experiences. i dont know if someone wrote about this, yet i could not find anywhere in this forum. When we share a "port" for example "s4 keyboard for s3", we say that we need root access in order to use this port. But when i think, if this apk files replace themselves with the original ones and rom thinks that they are the originals, why should we need root access? Of course we need recovery to flash them but do we absolutely need root? And i flashed 3 separate ports (keyboard, launcher and callrecord) into a fresh installed 4.3 MK6 stock rom without root and they worked... and still do... (scripts have to delete odex files automatically)
Installing a recovery will increase the binary counter and since your binary is up why not rooting right? But those who dont want to root their phone but still want to use the visuality, can install a recovery and flash the ports without rooting... Tested and proven...
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
alex.sg said:
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
Click to expand...
Click to collapse
If editing apps from rom then yes. But if you are flashing them through recovery you dont need root access for read and write permitions. Script also does that itself. Thats what im talking about
Galaxy S3 tapatalk 2 ile