Develop Bugs

[Q] How to remove stock apps

I found a guide around here before about how to remove system apps. Ive went through a couple of guides but cant seen to find it again. In the guide it had something along the lines of adb shell, the mounting the apps folder then removing them some how. Can anyone link me or know how to remove these apps such as friend stream. Thanks

under what circumstances are you trying to remove them??
i would advise a permroot, titanium backup and also about an hour, which apps do you want to remove?

Im fully rooted, s-off, recovery and all installed and i did remove the amazonmp3 app before but cant remember the command lines to do it
thanks

as far as ADB goes for me, im not too sure, unfortuantly,
i used the above method, and with that i removed all the bloatware i didnt want. i have S-Off , permroot and various other bits,
as you can see i cam from the X10i background and we didnt do a lot of custom roms and other bits there.

Thats ok, i tried using titanium backup to remove but didnt work for me so i was looking through these forums for the adb command line code, hopefully someone knows it lol

on titanium backup, you need to press the app you want to tremove for a while then itll bring up another menu, you need to do the recovery exploit uninstall, that will remove the app PERMANENTLY
give it a try youll see what i mean

SystemApp Remover is excellent, requires root.

what is root ?

MrGarak said:
SystemApp Remover is excellent, requires root.
Click to expand...
Click to collapse
Does it "brick" OTA updates like the TB method?

[Q] Unroot a custom rom?

Hey All,
For Work I need to install the app Good for Enterprise so I can get my calendar and work email pushed to my phone. Unfortunately it is company policy that it be unrooted. Presumeably a security issue. Is it possible to unroot a custom rom? i'd rather not go back to stock for the simple reason of app storage. I love A2SD+ and being able to have as many apps as I want installed. Also nandroid backups, that would go away without root too wouldn;t it? Can I just remove the SU.apk? Will that suffice to be "unrooted"? Is that even possible?

Tweak_four17 said:
Hey All,
For Work I need to install the app Good for Enterprise so I can get my calendar and work email pushed to my phone. Unfortunately it is company policy that it be unrooted. Presumeably a security issue. Is it possible to unroot a custom rom? i'd rather not go back to stock for the simple reason of app storage. I love A2SD+ and being able to have as many apps as I want installed. Also nandroid backups, that would go away without root too wouldn;t it? Can I just remove the SU.apk? Will that suffice to be "unrooted"? Is that even possible?
Click to expand...
Click to collapse
If you want to unroot, you'll need to go back to stock.
The reason they want unrooted phones, is not so much a security issue, as it is they just don't understand or don't wish to deal with possible problems.

If you backup your apps and data you can run the official RUU, and it will put the original unrooted system to your phone. I don't know other method.
Here are the official ROMs: http://shipped-roms.com/index.php?category=android&model=Bravo

Removing the SU binaries will unroot you, I don't see the need as to why you have to be unrooted though.

apparently you can't use the new movie-rental feature of google's market, when you are rooted.
Is it possible to stick to a custom rom but unroot it, so that google recognises your phone as a not-rooted device and allows you to watch movies from market?
I don't need root-permissions every day - in fact I only need it for Titanium Backup, so deleting su-binaries and/or superuser.apk would be ok - but it must be possible to restore them (via recovery/adb) to run TB.
This probably isn't what google wants you to do since you can download the movie to watch later and if you have a working recovery you probably could get you hands on the downloaded files, but still - would be nice, if this was possible.

Easiest way to unroot and go back to stock is to stick a PB99IMG.zip on your sdcard, and turn your phone on with volume held down

How about this:
1) Go back to stock ROM via RUU
2) Install Good For Enterprise (I guess your IT department installs this, so they can check you are not rooted?)
3) ROOT the stock ROM using UnRevoked
4) Take a Titanium Backup of Good For Enterprise
5) Re-install your custom ROM
6) Restore the Titanium Backup of GfE
-> You have a rooted, custom ROM with GfE installed. And your company will never know!

madcr0w said:
Easiest way to unroot and go back to stock is to stick a PB99IMG.zip on your sdcard, and turn your phone on with volume held down
Click to expand...
Click to collapse
Congratulations for not reading the post. Here is your cookie.
Sent from my HTC Desire using XDA Premium App

Demonic idea
kuroneko007 said:
How about this:
1) Go back to stock ROM via RUU
2) Install Good For Enterprise (I guess your IT department installs this, so they can check you are not rooted?)
3) ROOT the stock ROM using UnRevoked
4) Take a Titanium Backup of Good For Enterprise
5) Re-install your custom ROM
6) Restore the Titanium Backup of GfE
-> You have a rooted, custom ROM with GfE installed. And your company will never know!
Click to expand...
Click to collapse
I like your idea mate! Hahahahahaha....
Edit: Bad boy! Bad bad boy! hahahahahahahaha....

kuroneko007 said:
How about this:
1) Go back to stock ROM via RUU
2) Install Good For Enterprise (I guess your IT department installs this, so they can check you are not rooted?)
3) ROOT the stock ROM using UnRevoked
4) Take a Titanium Backup of Good For Enterprise
5) Re-install your custom ROM
6) Restore the Titanium Backup of GfE
-> You have a rooted, custom ROM with GfE installed. And your company will never know!
Click to expand...
Click to collapse
Has anyone ever tested this?

Or why don't you just delete superuser via adb or android commander

good for enterprise checks for root access/ su every time it starts. It's not an issue of not being able to install the app. It's available for free on the market. The problem is when entering all your info and starting it up, it checks for SU.
I am guessing the best way around this is to install custom rom, set everything up that you need that requires SU/root. Then delete all the su/root related files. Then install Good.
Unfortunately I don't have a list of all the files that have to be deleted for this to work.
There have been reports that other users who have tried this method got it to work but the App stopped syncing after a few days.

List:
/system/app/superuser
/system/bin/su
Sent from my HTC Desire using Tapatalk

I tried this method, renamed the 2 files. It has been working for last 24 hours. I'll update again after a week if it still works..
Edit:
yep this works perfectly.

vvelumm said:
I tried this method, renamed the 2 files. It has been working for last 24 hours. I'll update again after a week if it still works..
Edit:
yep this works perfectly.
Click to expand...
Click to collapse
You renamed SU.apk to SU.apk.bak most likely...
What did you rename the libs file to?

vvelumm said:
good for enterprise checks for root access/ su every time it starts. It's not an issue of not being able to install the app. It's available for free on the market. The problem is when entering all your info and starting it up, it checks for SU.
I am guessing the best way around this is to install custom rom, set everything up that you need that requires SU/root. Then delete all the su/root related files. Then install Good.
Unfortunately I don't have a list of all the files that have to be deleted for this to work.
There have been reports that other users who have tried this method got it to work but the App stopped syncing after a few days.
Click to expand...
Click to collapse
I have rooted my HTC Salsa to get apps2sd which is great, but now my mobile banking app says it will not work on a rooted device, similar to your issue.
I am new to android modding, what commands do i need to enter where to rename the files you mention ?
Thanks in advance.
Mike

wont work good enterprises would more than likely check every time like sky go. you would have to removed a2sd command line i think and all su binarys ( and su.akp ( difficult as its normally a system app and once one of the su has been removed you dont have premition to remove the other/
and to the donunt who said ( the dont understand root) wanna cookie 0. basicly good enterprise is a secure web client for companys to send information to mobiles, i have it on my work (iphone) <<<< scummmy.. anyways as root gives to the option to do what ever you or anyone else wants with the phone in theory you could use that system to breack the law or for instance chaindd could possible put an update in to su that will take data from the company> for google videos ) well with root you can screen record ( basicly ) excuse the spelling im trying to find out how to un root and keep all of my system ui mods and themes and my rom ( proving difficult)

hey I know that this is based on a old post but I have a question did you ever find out how to unroot a custom rom that is pre-rooted?

Rooted Desire keeps asking for Superuser permissions

I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.

Ommadawn said:
I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.
Click to expand...
Click to collapse
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef

Also, when being asked for permission, is "Remember" checked?

why not just re-root?

punky.mtp said:
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef
Click to expand...
Click to collapse
Yes you should have a list of allowed apps on opening the su app itself - click apps on top left. The allowed apps shouldn't keep requesting permission each time.
You coukkd uninstall su app then reinstall from market?
Nandroid backup first!

Thanks for the all the replies, much appreciated!
@punky.mtp & @stringer7: Yes, I can see the apps I've granted permissions to in the Superuser app, each has a green button against it. I'm not sure of the current version of SU I'm running, but I know it's not the latest version. I've tried to update it from the Market but it won't over-write the existing installed SU. I'm doing a nandroid as I type and will try uninstalling and reinstalling to see if that helps.
@HiVoltage85: Yes, I've set the remember checkbox as well for each app when granting permission.
@BigMrB: I've already re-rooted with different versions of unrevoked, several times, which hasn't fixed the problem.
I'll let you know how I go.

Sorry, I'm giving away my ignorance, but how do I uninstall my current Superuser app? The uninstall button is disabled in the manage applications part of the phone's setup.
Edit - Never mind, I found how to do it.

Looks like I have it fixed. I was able to remove the old Superuser app and install a new one from recovery (v2.3.6.3) which works properly and doesn't keep asking for permissions repeatedly. Thanks for the suggestions and help!

[Q]Busybox issues

So I was trying to downgrade my busybox to use the v6 Supercharger script. I had 1.19.3 installed. Was trying to go down to 1.18.3 I believe.
I used BusyBoxInstaller from the market to install the older one, and when it tried to download and install it said it didn't have the permissions and failed even though Superuser was allowing the app.
I figured it might of installed regardless so I went to ScriptManager and that wouldn't open, just FC. So I went back to BustBoxInstaller, and it started stating that my phone wasn't rooted and wouldn't open. I went to RootExplorer and that just hangs and then FC's. Restarted the phone, same issues. Tried a different busy box installer (BusyBox from the market) and it states some files are missing and it won't install either.
I used EsFile Explorer and I go into System/Xbin and it shows a busyBox file there, but I can't even mess with that. It can't be moved, renamed or anything. Not sure if it should even be messed with.
I tried searching this issue up around XDA, couldn't find anything similar.
Anyhow, did I just mess up pretty good and do I need to reflash my ROM? or is there a quick fix without all the mess?

I think I would reflash the ROM, then use the busybox installer on a fresh flash, before you restore anything, to install the version of busybox that you want

There are two busybox installers that I'm aware of, have you tried both? I prefer the newer one on the market - I think it's by jrummy. Also make sure the install location is correct.
If you've somehow reverted to s-on then the file won't install either. I doubt this is the case but I remember one case of someone having issues with something to do with a file in system and after trying everything they finally realized they were somehow s-on.
Supersonic Evo 4G | MIUI | Tapatalk

plainjane said:
There are two busybox installers that I'm aware of, have you tried both? I prefer the newer one on the market - I think it's by jrummy. Also make sure the install location is correct.
If you've somehow reverted to s-on then the file won't install either. I doubt this is the case but I remember one case of someone having issues with something to do with a file in system and after trying everything they finally realized they were somehow s-on.
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
This is true quoted for truth!

I checked and I'm s-off. I used both busybox apps. The one from rummy won't even open. It states I'm not rooted and then closes. The other app (just called busybox) opens but when I hit install it basically states the same thing. I can't choose the install location on that one either. I saw something about pushing it with ABD tool. Just not at home to try that out. Thanks for the help guys. Probably gonna have to wipe and start over.
Sent from my PC36100 using XDA App

I have this same issue. Ever since the busybody updated I cannot do anything. I can't go into root explorer, install any apks will not connect to wifi or wimax

Want to point out a few things, if your running scripts use Busybox 1.18.2. Secondly, the app in the market, Busynox Installer works wonder, however, sometimes when you change the version number it doesn't stick. Today, I had to cycle through installing 1.18.2 four times until it stuck. After installing another version, use root check to verify the version of busybox installed before proceeding to using any scripts. Also, check with the rom your using and make sure theres no issues. Each rom behaves differently.

JollyGrnReefer said:
Want to point out a few things, if your running scripts use Busybox 1.18.2. Secondly, the app in the market, Busynox Installer works wonder, however, sometimes when you change the version number it doesn't stick. Today, I had to cycle through installing 1.18.2 four times until it stuck. After installing another version, use root check to verify the version of busybox installed before proceeding to using any scripts. Also, check with the rom your using and make sure theres no issues. Each rom behaves differently.
Click to expand...
Click to collapse
Thanks for the help. Again though I can't get into BusyBox Installer or BusyBox app (both from the market) So I really don't have a choice to get it to stick or to pick where it installs. I wound up having to just go back and recover off an old ROM backup I had.
I did try go back to 1.18.2 but BusyBox Installer (the one by Rummy) for some reason it wouldn't install. It kept saying that I didn't have permission and then another pop-up would come saying "superuser access permitted" or something like that. I hit install a few times, and kept getting the same error. I figured it was just a bug in the app. I tried going into the Script manager but it would FC without opening. I then tried going back into BusyBox installer which then claimed that I wasn't rooted (even though I show S-Off) and then would close. I then tried going into RootExplorer to delete the script thinking that might be the issue. Root Explorer would just hang. It'd stay on a black screen..say "this is taking longer then normal. Force close or wait" I hit wait 3 times, and no luck. Tried restarting multiple times, same issues.
Earlier today it stared effecting my connectivity or so I assume because all of a sudden I'd be roaming, the not, then I would be again..on and off all day. I never had that issue on that ROM before this whole busybox issue.
Anyhow. Again, I just reverted back to the old ROM I had and am going to sit on it for a bit.
Thanks to everyone for the help, ideas, tips, etc. It's greatly appreciated.

[Q] Upgraded to 4.1.1 and lost rooting capability

I rooted my AT&T i747 with Android 4.0.4 a couple months ago and installed SuperSU as well and was working great. When I upgraded my phone to android 4.1.1 a few days ago I lost all rooting capabilities. My Titanium Backup Pro no longer has root access as well as my SuperSU and a couple of other apps that require it. I also have tried uninstalling SuperSU with no success.
Could I just reflash my i747 just like I did back on 4.0.4 to root it again or is there a way to correct the current root access? What would you recommend?
Thanks in advance!

If you took the official update then you have lost root. You just need to re root and you will be back in business.
Sent from my SGH-I747M using xda app-developers app

jbradbury said:
If you took the official update then you have lost root. You just need to re root and you will be back in business.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I want to do it but this is what the app says on Google play...
"NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU."
Does that mean I will lose root for good if I just try to reroot it a second time without first uninstalling it? That is where I am having trouble as well. The app will not let me properly uninstall it from within the app.
Thanks.

SCADAman said:
I want to do it but this is what the app says on Google play...
"NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU."
Does that mean I will lose root for good if I just try to reroot it a second time without first uninstalling it? That is where I am having trouble as well. The app will not let me properly uninstall it from within the app.
Thanks.
Click to expand...
Click to collapse
That warning by Chainfire relates to the various other superuser shells out there (like superuser.apk, ROM-specific superuser shells). Wait, what's the shell? Let me explain:
OK, so having root means you have three folders/files available:
superSU.apk (the shell; it's an interface lets you allow certain apps access to the actual superuser files..think of it as the root gatekeeper..having it alone does not mean you're rooted...seems like you have this)
/system/xbin/su/ (folder with files SPECIFIC to SuperSU.apk...apps can ask superSU.apk to access these "root-enabling" files ...you lost this)
/system/bin/su (folder with files SPECIFIC to SuperSU.apk...apps can ask superSU.apk to access these "root-enabling" files...you lost this, too)
The latter two, the folders, are collectively referred as su binaries. His warning: if don't like using superSU.apk as your shell, do not simply uninstall superSU.apk. Why? I'm not totally sure, but I think it's because that will leave the su binaries, specific to his app! Then, when an app wants to ask for root, it doesn't know what the flip to do. It has to interact with the shell, but the shell is missing!
The special method to really remove root is:
creepyncrawly said:
You can remove root by using a root file explorer to remove /system/app/superuser, /system/bin/su and /system/xbin/su. After you reboot, you'll not longer be rooted.
Click to expand...
Click to collapse
OK, the "what is going on behind the scenes" is over. To get root back:
Basically, you need to replace the su binaries. But, the only way I know how is to replace all three of those parts. I'm pretty sure you're fine to "overwrite" the 1/3 of root you already have (SuperSU.apk). Thus, you have two main options:
1) Use CF AutoRoot (http://forum.xda-developers.com/showthread.php?t=1963790). It will temporarily flash a modified recovery, and then add those binaries and the SuperSU.apk, and then flash the stock recovery back, but it will trip the flash counter. Takes 30 seconds. Should be safe, because it will just overwrite the apk and add the su binaries. [I rooted this way; triangle away is cheap to reset the flash counter!]
2) Use Mr. Robinson's method (http://forum.xda-developers.com/showthread.php?t=1739426). This contain a /system image with all three aforementioned parts. Will take about 15 minutes, but will not trip the flash counter. As long as you're on stock firmware (which I think you are), this won't delete any apps/data.

I got it rooted again. Thanks for help guys. I just reinstalled the supersu.apk and the binary files and it's rooted once again. Whoo-hoo!